Please do a search on 'configuration Management' to see what it means.
A brief general definition:
"A discipline that applies technical and administrative direction and surveillance over the lifecycle of items"
It relates to test in several ways:
1. No code should be delivered into a test environment that has not been subject to configuration management.
2. All test deliverables should enter/pass through a form of configuration management before being released.
3. All project documentation should enter/pass through a form of configuration management. In this respect it is a method of fixing the scope!
When an application is first developed and released to testing, it should most likely be released as Rev 1.00.00 Then as it is reworked to remove defects it subsequently changes to Rev 1.00.01, 1.00.02, etc. until it is ready for release. Once it is released, depending on wether it is a rewrite or enhancement, or even just a defect repair, patches or new releases are delivered to the customer and each has its own Configuration Management label such as Service patch 1.01.02 There are several methods of numbering usually determined by the Company and the development team. But it is essential that these updates, patches, and Revisions be tracked and issued in accordance with policy. There for Configuration Management should be an integral part of the Software life cycle and very important to testing so that they are aware of exactly what they have tested and failed or passed for release.