Configuration management (CM) in the context of testing involves the process of managing changes to the software and its associated artifacts, such as test plans, test cases, test scripts, and test results. It ensures that all changes are systematically tracked and controlled throughout the software development lifecycle.
* Option A: Incorrect. While CM supports consistency in test environments, it is not specifically about comparing expected and actual results.
* Option B: Correct. CM allows tracking all changes to versions of testware, ensuring that the correct versions are used and any changes are documented and managed.
* Option C: Incorrect. This describes quality management, not configuration management.
* Option D: Incorrect. Configuration management does not focus on configuring static analysis tools.