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 testing within those levels for an
organization or program.
Test Approach – The implementation of the
test strategy for a specific project. It typically includes the decisions made
based on the project’s goal and the risk assessment carried out, starting
points regarding the process, the test design techniques to be applied, exit
criteria and test types to be performed.
Coverage (Test Coverage) – The degree, expressed as a
percentage, to which a specified coverage item has been exercised by a test
suite.
Exit Criteria – The set of generic and
specific conditions, agreed upon with 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 by testing to report
against and to plan when to stop testing.
Test Control – A test management task that
deals with developing and applying a set of corrective actions to get a test
project on track when monitoring shows a deviation from what was planned.
Test Monitoring – A test management task that
deals with the activities related to periodically checking the status of a test
project. Reports are prepared that compare the actual status to that which was
planned.
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 Design Specification – A document specifying the
test conditions (coverage items) for a test item, the detailed test approach and
the associated high–level test cases.
Test Procedure Specification (Test
Script, Manual Test Script)
– A document specifying a sequence of actions for the execution of a test.
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 Execution – The process of running a
test by the component or system under test, producing actual results.
Test Log – A chronological record of
relevant details about the execution of tests.
Incident – Any event occurring that
requires investigation.
Re-testing / Confirmation
Testing – Testing
that runs test cases that failed the last time they were run, in order to
verify the success of corrective actions.
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.
OR
It
is the testing done to ensure that changed functionality is not affecting
unchanged functionality.
Test Summary Report – A document summarizing
testing activities and results. It also contains an evaluation of the
corresponding test items against exit criteria.
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.
Independence – Separation of responsibilities,
which encourages the accomplishment of objective testing.
