A-Z Knowledge in Testing - T Series

[karthick]

A-Z Knowledge in Testing - T Series

Test log   

A chronological record of relevant details about the execution of tests.

Test manager   

The person responsible for testing and evaluating a test object. The individual, who directs, controls, administers plans and regulates the evaluation of a test object.

Test object   

The component or system to be tested.

Test point analysis (TPA)   

A formula based test estimation method based on function point analysis.

Test procedure specification   

A document specifying a sequence of actions for the execution of a test. Also known as test script or manual test script.

Test process   

The fundamental test process comprises planning, specification, execution, recording and checking for completion.

Test run   

Execution of a test on a specific version of the test object.

Test specification

A document that consists of a test design specification, test case specification and/or test procedure specification.

Test strategy   

A high-level document defining the test levels to be performed and the testing within those levels for a programme (one or more projects).

Test suite   

A set of several test cases for a component or system under test, where the post condition of one test is often used as the precondition for the next one.

Test type   

A group of test activities aimed at testing a component or system regarding one or more interrelated quality attributes.
A test type is focused on a specific test objective, i.e. reliability test, usability test, regression test etc., and may take place on one or more test levels or test phases.

Testability   

The capability of the software product to enable modified software to be tested.

Tester   

A technically skilled professional who is involved in the testing of a component or system.

Testing   

The process of exercising software to verify that it satisfies specified requirements and to detect faults

Thread testing   

A version of component integration testing where the progressive integration of components follows the implementation of subsets of the requirements, as opposed to the integration of components by levels of a hierarchy.

Top-down testing

An incremental approach to integration testing where the component at the top of the component hierarchy is tested first, with lower level components being simulated by stubs.

Tested components are then used to test lower level components.

Traceability   

The ability to identify related items in documentation and software, such as requirements with associated tests. See also horizontal traceability, vertical traceability.