1
A document that describes in detail the characteristics of the product with regard to its intended features.
2
Testing where components or systems are integrated and tested one or some at a time, until all the components or systems are integrated and tested.
3
Testing of individual software components.
4
Retesting a previously tested program following modification to ensure that faults have not been introduced or uncovered as a result of the changes made.
5
A document showing the relationship between Test Requirements and Test Cases.
6
Testing employing software tools which execute tests without manual intervention. Can be applied in functional, regression, performance, etc. testing. The use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions.
7
is a commonly used term for a specific test. This is usually the smallest unit of testing. This will consist of information such as requirements testing, test steps, verification steps, prerequisites, outputs, test environment, etc.
8
A document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks, who will do each task, and any risks requiring contingency planning.
9
Testing that involves the execution of the software of a component or system.
10
Commonly used to refer to the instructions for a particular test that will be carried out by an automated test tool.
11
Most used tool to keep "production control"
12
A fault in a program which causes the program to perform in an unintended or unanticipated manner
