Software Testing Glossary

It is the discussion aiming to develop a common approach to a technical process and conducted by equal participants.

A set of one or more test cases.

The implementation of a certain test strategy for a specific project.

(1) A person who provides guidance and strategic direction for a test organization and for its relationship with other disciplines.

Using the software to implement or assist in carrying out certain test processes, such as test management, test design, test execution and test results.

Document on the basis of which requirements for a component or system specified. Test scenarios are based on this documentation. If editing of this document possible only in the process of formal amendment procedure, then such a basis is called a frozen test basis.

It is the set of input values, execution preconditions, expected results and execution postconditions, developed for a particular purpose or test condition, such as performing a certain program path or validating for compliance to certain requirement.

A document describing a set of test cases, the purpose, inputs, test actions, expected results and execution preconditions for the object under testing.

Account of software testing objectives and ideas about the testing process. It is usually used in exploratory testing.

During the phase of software testing complete, it is collect data on all completed processes with a goal to combining the expertise, test support, facts and numbers.