5 Written questions
5 Matching questions
- defect based test design technique
- design-based testing
- coverage analysis
- state table
- a Measurement of achieved coverage to a specified coverage item during test execution referring to predetermined criteria to determine whether additional testing is required and if so, which test cases are needed.
- b A procedure to derive and/or select test cases targeted at one or more defect categories, with tests being developed from what is known about the specific defect category. See also defect taxonomy. A system of (hierarchical) categories designed to be a useful aid for reproducibly classifying defects.
- c A grid showing the resulting transitions for each state combined with each possible event, showing both valid and invalid transitions.
- d An approach to testing in which test cases are designed based on the architecture and/or detailed design of a component or system (e.g. tests of interfaces between components or systems).
- e The process of confirming that a component, system or person complies with its specified requirements, e.g. by passing an exam.
5 Multiple choice questions
- A black box test design technique in which test cases are designed to execute business procedures and processes. [TMap] See also procedure testing. Testing aimed at ensuring that the component or system can operate in conjunction with new or existing users' business procedures or operational procedures.
- Comparison of actual and expected results, performed while the software is being executed, for example by a test execution tool.
- A test design technique in which a model of the statistical distribution of the input is used to construct representative test cases. See also operational profile testing. Statistical testing using a model of system operations (short duration tasks) and their probability of typical use. [Musa]
- A set of one or more test cases. [IEEE 829]
- See white-box testing. Testing based on an analysis of the internal structure of the component or system.
5 True/False questions
benchmark test → Any event occurring that requires investigation. [After IEEE 1008]
multiple condition coverage → The percentage of combinations of all single condition outcomes within one statement that have been exercised by a test suite. 100% multiple condition coverage implies 100% condition determination coverage.
test phase → A distinct set of test activities collected into a manageable phase of a project, e.g. the execution activities of a test level. [After Gerrard]
non-functional requirement → The capability of the software product to provide functions which meet stated and implied needs when the software is used under specified conditions. [ISO 9126]
blocked test case → A test case that cannot be executed because the preconditions for its execution are not fulfilled.