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






2. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.






3. The capability of a software product to provide agreed and correct output with the required degree of precision






4. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.






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






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






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






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






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






10. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance






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






12. Combining components or sytems into larger structural units or subsystems.






13. Components at lowest level are tested first with higher-level components simulated by drivers. Tested components are then used to test higher-level components. Repeat until all levels have been tested.






14. White-box design technique used to design test cases for a software component using LCSAJ.






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






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






17. A review not based on a formal documented procedure






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






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






20. Measures amount of testing performed by a collection of test cases






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






22. Human action that generates an incorrect result.






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






24. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan






25. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






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






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






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






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






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






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






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






39. A task of maintaining and controlling changes to all entities of a system.






40. One defect prevents the detection of another.






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






42. A component of the incident report that determines the actual effect of the incident on the software and its users.






43. Testing software components that are separately testable. Also module program and unit testing.






44. Deviation of a software system from its expected delivery services or results






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






46. Response of the application to an input






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






48. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.






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






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