Test your basic knowledge |

Instructions:
  • Answer 50 questions in 15 minutes.
  • If you are not ready to take this test, you can study here.
  • Match each statement with the correct term.
  • Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. Combining components or sytems into larger structural units or subsystems.






2. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)






3. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure






4. Components are integrated in the order in which they are developed






5. Integration approach components or subsystems are combined all at once rather than in stages.






6. Incident Report - Identifier - Summary - Incident - Description - Impact






7. Insertion of additional code in the existing program in order to count coverage items.






8. Severity - Priority






9. An event or item that can be tested using one or more test cases






10. Based on the generic iterative-incremental model. Teams work by dividing project tasks into small increments involving only short-term planning to implement various iterations






11. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.






12. Black-box testing technique used to create groups of input conditions that create the same kind of output.






13. Simple & easy to follow Its rigidity makes it easy to follow It's typically well planned - Systematic - Freezing requirements before development begins ensures no rework later Each phase has specific deliverables






14. Used to test the functionality of software as mentioned in software requirement specifications.






15. The smallest software item that can be tested in isolation.






16. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance






17. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.






18. Software products or applications designed to automate manual testing tasks.






19. Tools used to store and manage incidents return phone defects failures or anomalies.






20. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.






21. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.






22. Based on analysis of functional specifications of a system.






23. All possible combinations of input values and preconditions are tested.






24. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing






25. Events that occurred during the testing process our investigation.






26. The ratio between the number of defects found and the size of the component/system tested.






27. A review not based on a formal documented procedure






28. A table showing combinations of inputs and their associated actions.






29. Allows storage of test input and expected results in one or more central data sources or databases.






30. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed






31. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first






32. Special additions or changes to the environment required to run a test case.






33. Develop & proiroitize test cases Create groups of test cases Set up test environment






34. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)






35. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.






36. Sequence in which instructions are executed through a component or system






37. A functional testing approach in which test cases are designed based on business processes.






38. Abilitiy of software to collaborate with one or more specified systems subsystem or components.






39. Testing performed to determine whether the system meets acceptance criteria






40. Increased load (transations) used to test behavior of system under high volume.






41. Components are combined and tested in the order in which basic functionalities start working






42. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.






43. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.






44. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports






45. Tools used to keep track of different versions variants and releases of software and test artifacts (such as design documents test plans and test cases).






46. Human action that generates an incorrect result.






47. Occurrences that happen before and after an unexpected event






48. Integrate different kinds of tools to make test management more efficient and simple.






49. Input or combination of inputs required to test software.






50. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.