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. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.






2. A review not based on a formal documented procedure






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






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






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






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






7. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools






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






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






10. Conditions required to begin testing activities.






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






12. One defect prevents the detection of another.






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






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






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






16. Tools used by developers to identify defects in programs.






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






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






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






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






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






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






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






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






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






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






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






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






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






30. Waterfall iterative-incremental "V"






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






32. Record details of test cases executed Record order of execution record results






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






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






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






36. Actual inputs required to execute a test case






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






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






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






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






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






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






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






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






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






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






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






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






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






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