test closure activities code example

Example 1: test closure activities

Test Completion Check: 
To ensure all tests should be either run
or deliberately skipped and all known
defects should be either fixed,
deferred for a future release or
accepted as a permanent restriction.

Test Artifacts handover: 
Tests and test environments should be
handed over to those responsible for
maintenance testing. Known defects accepted
or deferred should be documented and
communicated to those who will use
and support the use of the system.

Lessons learned: Analyzing lessons learned
to determine changes needed for future
releases and projects. In retrospective
meetings, plans are established 
to ensure that good practices can be
repeated and poor practices are not repeated

Archiving results, logs, reports, and 
other documents and work products in the CMS
(configuration management system).

Example 2: test closure

What is Test Closure?
Test Closure is the note prepared
before test team formally completes
the testing process. This note contains
the total no. of test cases, total no.
of test cases executed, total no. of
defects found, total no. of defects fixed,
total no. of bugs not fixed,
total no of bugs rejected etc.,