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. Black-box testing technique used to create groups of input conditions that create the same kind of output.






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






3. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers






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






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






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






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






8. A review not based on a formal documented procedure






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






10. Tracing requirements for a level of testing using test documentation from the test plan to the test script.






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






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






13. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.






14. One defect prevents the detection of another.






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






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






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






18. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram






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






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






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






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






23. Requirements that determine the functionality of a software system.






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






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






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






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






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






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






30. Waterfall iterative-incremental "V"






31. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






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






39. Tests interfaces between components and between integrated components and systems.






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






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






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






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






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






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






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






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






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






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






50. Integration Approach: A frame or backbone is created and components are progressively integrated into it.