A two-dimensional table, which correlates two entities (e.g., requirements and test cases). The table allows tracing back and forth the links of one entity to the other, thus enabling the determination of Coverage achieved and the assessment of impact of proposed changes.
The ability to identify related items in documentation and software, such as requirements with associated tests. See also horizontal traceability, vertical traceability.
Artifacts produced during the test process required to plan, design, and execute tests, such as documentation, scripts, inputs, expected results, set-up and clear-up procedures, files, databases, environment, and any additional software or utilities used in Testing. [After Fewster and Graham]
The process consisting of all lifecycle 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.
A skilled professional who is involved in the Testing of a component or system.
The capability of the software product to enable modified software to be tested.
A way of developing software where the test cases are developed, and often automated, before the software is developed to run those test cases.
A group of test activities aimed at Testing a component or system focused on a specific test objective, i.e. functional test, usability test, regression test etc. A test type may take place on one or more test levels or test phases. [After TMap]
A document summarizing Testing activities and results. It also contains an evaluation of the corresponding test items against Exit criteria. [After IEEE 829]
A high-level description of the test levels to be performed and the Testing within those levels for an organization or programme (one or more projects).