5 Written questions
5 Matching questions
- cause-effect graph
- multiple condition
- serviceability testing
- a A graphical representation of inputs and/or stimuli (causes) with their associated outputs (effects), which can be used to design test cases.
- b See compound condition. Two or more single conditions joined by means of a logical operator (AND, OR or XOR), e.g. 'A>B AND C>1000'.
- c See maintainability testing. The process of testing to determine the maintainability of a software product.
- d See error. A human action that produces an incorrect result. [After IEEE 610]
- e The capability of the software product to be installed in a specified environment [ISO 9126]. See also portability. The ease with which the software product can be transferred from one hardware or software environment to another. [ISO 9126]
5 Multiple choice questions
- A variable (whether stored within a component or outside) that is read by a component.
- An analysis method that determines which parts of the software have been executed (covered) by the test suite and which parts have not been executed, e.g. statement coverage, decision coverage or condition coverage.
- An attribute of a test indicating whether the same results are produced each time the test is executed.
- The percentage of all single condition outcomes that independently affect a decision outcome that have been exercised by a test case suite. 100% condition determination coverage implies 100% decision condition coverage.
- The process of evaluating behavior, e.g. memory performance, CPU usage, of a system or component during execution. [After IEEE 610]
5 True/False questions
decision testing → A white box test design technique in which test cases are designed to execute decision outcomes.
incident management tool → A tool that facilitates the recording and status tracking of incidents. They often have workflow-oriented facilities to track and control the allocation, correction and re-testing of incidents and provide reporting facilities. See also defect management tool. A tool that facilitates the recording and status tracking of defects and changes. They often have workflow-oriented facilities to track and control the allocation, correction and re-testing of defects and provide reporting facilities.
robustness testing → Test execution carried out by following a previously documented sequence of tests.
orthogonal array testing → Testing by means of a random selection from a large range of inputs and by randomly pushing buttons, ignorant on how the product is being used.
test type → The individual element to be tested. There usually is one test object and many test items. See also test object. A reason or purpose for designing and executing a test.