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. Testing software components that are separately testable. Also module program and unit testing.






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






3. A unique identifier for each incident report generated during test execution.






4. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).






5. Specific groups that represent a set of valid or invalid partitions for input conditions.






6. Component - Integration - System - Acceptance






7. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.






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






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






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






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






12. Waterfall iterative-incremental "V"






13. Informal testing technique in which test planning and execution run in parallel






14. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.






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






16. Human action that generates an incorrect result.






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






18. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.






19. Conditions ensuring testing process is complete and the object being tested is ready for next stage.






20. Special-purpose software used to simulate a component called by the component under test






21. Testing software in its operational environment






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






23. The process of finding analyzing and removing causes of failure in a software product.






24. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.






25. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.






26. An analysis that determines the portion of code on software executed by a set of test cases






27. Special-purpose software used to simulate a component that calls the component under test






28. Operational testing performed at an _external_ site without involvement of the developing organization.






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






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






31. A document that records the description of each event that occurs during the testing process and that requires further investigation






32. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.






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






34. Sequence in which data items are accessed or modified by code.






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






36. 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).






37. A set of conditions that a system needs to meet in order to be accepted by end users






38. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.






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






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






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






42. Used to replace a component that calls another component.






43. 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






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






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






46. Separation of testing responsibilities which encourages the accomplishment of objective testing






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






48. Behavior or response of a software application that you observe when you execute the action steps in the test case.






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






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