5 Written Questions
5 Matching Questions
- test logging
- test summary report
- abstract test case
- test schedule
- a See high level test case. A test case without concrete (implementation level) values for input data and expected results. Logical operators are used; instances of the actual values are not yet defined and/or available.
- b The process of recording information about tests executed into a test log.
- c A document summarizing testing activities and results. It also contains an evaluation of the corresponding test items against exit criteria. [After IEEE 829]
- d See test comparator.A test tool to perform automated test comparison of actual results with expected results.
- e A list of activities, tasks or events of the test process, identifying their intended start and finish dates and/or times, and interdependencies.
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.
- The planning, estimating, monitoring and control of test activities, typically carried out by a test manager.
- 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.
- The person responsible for project management of testing activities and resources, and evaluation of a test object. The individual who directs, controls, administers, plans and regulates the evaluation of a test object.
- The capability of the software product to provide appropriate performance, relative to the amount of resources used under stated conditions. [ISO 9126]
5 True/False Questions
structurebased testing → See white-box testing. Testing based on an analysis of the internal structure of the component or system.
incremental testing → A black box test design technique where test cases are selected, possibly using a pseudo-random generation algorithm, to match an operational profile. This technique can be used for testing non-functional attributes such as reliability and performance.
concurrency testing → Testing to determine the security of the software product. See also functionality testing. The process of testing to determine the functionality of a software product.
documentation testing → A white box test design technique in which test cases are designed to execute condition outcomes.
performance → The level of (business) importance assigned to an item, e.g. defect.