5 Written Questions
5 Matching Questions
- basis test set
- risk level
- problem report
- a See error. A human action that produces an incorrect result. [After IEEE 610]
- b The importance of a risk as defined by its characteristics impact and likelihood. The level of risk can be used to determine the intensity of testing to be performed. A risk level can be expressed either qualitatively (e.g. high, medium, low) or quantitatively.
- c A set of test cases derived from the internal structure of a component or specification to ensure that 100% of a specified coverage criterion will be achieved.
- d The ability of the software product to perform its required functions under stated conditions for a specified period of time, or for a specified number of operations. [ISO 9126]
- e See defect report. A document reporting on any flaw in a component or system that can cause the component or system to fail to perform its required function. [After IEEE 829]
5 Multiple Choice Questions
- See fault seeding.error seeding tool: See fault seeding tool. The process of intentionally adding known defects to those already in the component or system for the purpose of monitoring the rate of detection and removal, and estimating the number of remaining defects. [IEEE 610]
- The implementation of the test strategy for a specific project. It typically includes the decisions made that follow based on the (test) project's goal and the risk assessment carried out, starting points regarding the test process, the test design techniques to be applied, exit criteria and test types to be performed.
- Testware used in automated testing, such as tool scripts.
- The degree, expressed as a percentage, to which a specified coverage item has been exercised by a test suite.
- See result. The consequence/outcome of the execution of a test. It includes outputs to screens, changes to data, reports, and communication messages sent out
5 True/False Questions
portability → The ease with which the software product can be transferred from one hardware or software environment to another. [ISO 9126]
testable requirements → The degree to which a requirement is stated in terms that permit establishment of test designs (and subsequently test cases) and execution of tests to determine whether the requirements have been met. [After IEEE 610]
defect tracking tool → A tool used by programmers to reproduce failures, investigate the state of programs and find the corresponding defect. Debuggers enable programmers to execute programs step by step, to halt a program at any program statement and to set and examine program variables.
installability → A high level document describing the principles, approach and major objectives of the organization regarding testing.
test log → A chronological record of relevant details about the execution of tests. [IEEE 829]