Dream... Passion... More than...!!!

Confirmation Testing, Re-Testing
Testing that runs test cases that failed the last time they were run, in order to verify the success of corrective actions.

Exit Criteria
The set of generic and specific conditions, agreed upon with the stakeholders, for permitting a process to be officially completed. The purpose of exit criteria is to prevent a task from being considered completed when there are still outstanding parts of the task which have not been finished. Exit criteria are used to report against and to plan when to stop testing. [After Gilb and Graham]

Incident
Any event occurring that requires investigation. [After IEEE 1008]

Regression Testing
Testing of a previously tested program following modification to ensure that defects have not been introduced or uncovered in unchanged areas of the software, as a result of the changes made. It is performed when the software or its environment is changed. 

Test Basis
All documents from which the requirements of a component or system can be inferred. The documentation on which the test cases are based. If a document can be amended only by way of formal amendment procedure, then the test basis is called a frozen test basis. [After TMap]

Test Condition
An item or event of a component or system that could be verified by one or more test cases, e.g. a function, transaction, feature, quality attribute, or structural element.

Test Coverage
The degree, expressed as a percentage, to which a specified coverage item has been exercised by a test suite

Test Data
Data that exists (for example, in a database) before a test is executed, and that affects or is affected by the component or system under test.

Test Execution
The process of running a test on the component or system under test, producing actual result(s). 

Test Log
A chronological record of relevant details about the execution of tests. [IEEE 829]

Test Plan
A document describing the scope, approach, resources and schedule of intended test activities. It identifies amongst others test items, the features to be tested, the testing tasks, who will do each task, degree of tester independence, the test environment, the test design techniques and entry and exit criteria to be used, and the rationale for their choice, and any risks requiring contingency planning. It is a record of the test planning process. [After IEEE 829] 

Test Procedure, 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. [After IEEE 829]

Test Policy
A high level document describing the principles, approach and major objectives of the organization regarding testing.

Test Strategy
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).

Test Suite, Test Set
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 Summary Report
A document summarizing testing activities and results. It also contains an evaluation of the corresponding test items against exit criteria. [After IEEE 829]

Testware
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]