Test closure activities : 

During test closure activities, we collect data from completed test activities to consolidate experience, including checking and filing testware, and analyzing facts and numbers. We may need to do this when software is delivered. We also might close testing for other reasons, such as when we have gathered the infor-mation needed from testing, when the project is cancelled, when a particular milestone is achieved, or when a maintenance release or update is done.

Test closure activities include the following major tasks:

1.)  Check which planned deliverables we actually delivered and ensure all incident reports have been resolved through defect repair or deferral.

2.)  Finalize and archive testware, such as scripts, the test environment, and any other test infrastructure, for later reuse.

3.)  Hand over testware to the maintenance organization who will support the software and make any bug fixes or maintenance changes, for use in con firmation testing and regression testing.

4.) Evaluate how the testing went and analyze lessons learned for future releases and projects.