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. The ratio between the number of defects found and the size of the component/system tested.






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






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






4. Find defects in code while the software application being tested is running.






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






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






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






8. One defect prevents the detection of another.






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






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






11. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.






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






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






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






15. Human action that generates an incorrect result.






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






17. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes






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






19. Black-box test design technique - test cases are designed from a decision table.






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






21. Conditions required to begin testing activities.






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






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






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






25. A type of review that involves visual examination of documents to detect defects such as violations of development standards and non-conformance to higher-level documentation.






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






27. Component - Integration - System - Acceptance






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






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






30. Ability of software to provide appropriate performance relative to amount of resources used.






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






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






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






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






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






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






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






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






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






40. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components






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






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






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






44. Occurrences that happen before and after an unexpected event






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






46. Extract data from existing databases to be used during execution of tests make data anonymous generate new records populated with random data sorting records constructing a large number of similar records from a template






47. Tools used to identify and calculate coverage items in program code.






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






49. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.






50. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".