Test Execution

Test execution begins once the test object is delivered and the entry criteria to
test execution are satisfied. Tests should be designed or at least defined prior
to test execution. Tools should be in place, particularly for test management,
defect tracking and (if applicable) test execution automation. Test results
tracking, including metrics tracking, should be working and the tracked data
should be understood by all team members. Standards for test logging and
defect reporting should be available and published. By ensuring these items
are in place prior to test execution, the execution can proceed efficiently.

Tests should be executed according to the test cases, although the Test
Manager should consider allowing some amount of latitude so that the tester
can cover additional interesting test scenarios and behaviours that are
observed during testing. When following a test strategy that is at least in part
reactive, sometime should be reserved for test sessions using experience-
based and defect-based techniques. Of course, any failure detected during
such unscripted testing must describe the variations from the written test case
that are necessary to reproduce the failure. Automated tests will follow their
defined instructions without deviation.

The main role of a Test Manager during test execution is to monitor progress
according to the test plan and, if required, to initiate and carry out control
actions to guide testing toward a successful conclusion in terms of mission,
objectives, and strategy. To do so, the Test Manager can use traceability from
the test results back to the test conditions, the test basis, and ultimately the
test objectives, and also from the test objectives forward to the test results.