Chapter 1 terminology Flashcards
Defect
A flaw in a component or system that can cause the component or system to fail to perform its required function. A defect if encountered during execution may cause a failure of the component or system.
Bug
See defect
Error
(Mistake): A human action that produces an incorrect result
Fail
A test is deemed to fail if it’s actual result does not match its expected result.
False fail result
A test result in which a defect is reported although no such defect actually exists in the test object.
False positive result
See false fail result
Failure
Deviation of the component or system from its expected delivery, service or result.
Fault
Defect or bug
Mistake
See error
Pass
A test is deemed to pass if it s actual result matches its expected result.
False negative result
A test result which fails to identify the presence of a defect that is actually present in the test object.
Quality
The degree to which a component system or process meets specified requirements and or user/ customer needs and expectations.
Risk
A factor that could result in future negative consequences, usually expressed as impact or likelihood.
Testing
The process consisting of all life cycle activities both static and dynamic, concerned with planning preparation and evaluation of software products and related work products to determine that they satisfy specified requirements, to demonstrate that they are fit for purpose and to detect defects.
Requirements
A condition or capability needed by a user to solve a problem or achieve an objective that must be met or possessed by a system or system component to satisfy a contract, standard, specification or other formally imposed document
Review
An evaluation of a product or project status to ascertain discrepancies from planned results and to recommend improvements. Examples, management review, informal review, technical review, inspection and walk through
Debugging
The process of finding analyzing and removing the causes of failures in software
Confirmation testing
Testing that runs test cases that failed the last time they were run in order to verify the success of corrective actions
Test strategy
A high-level description of the test levels to be performed and the testing within those levels for an organization or program (One or more projects).
Exhaustive testing
A test approach in which the test sweet comprises all combinations of input values and preconditions.
Test execution
The process of running a test on the component or system under test, producing actual results.
Test approach
The implementation of the test strategy for a specific project. It typically includes the decisions made that follow based on the (test) projects goal and the risk assessment carried out, starting points regarding the test process, the test design techniques to be applied, exit criteria and types to be performed.
