Configuration Management in Software Testing
by Nataliia Vasylyna | October 26, 2011 10:00 am
Configuration management is the detailed recording and updating of information for software and hardware components.
Components are not only source code. It can also be tracking of modifications for software documents such as:
- Requirement
- Design
- Test cases[1]
- Test plans
As soon as modifications are performed in adhoc[2] and in an uncontrollable style chaotic conditions can arise and more errors appeared. So modifications should be performed in a controlled fashion and with appropriate versioning.
We should have an opportunity to return back to the old version at any convenient moment of time.
The major purpose of configuration management is to track our modifications if we have issues with the current system. Configuration management is done using baselines.
Learn more from QATestLab
Related Posts:
- Test cases: https://qatestlab.com/resources/knowledge-center/sample-deliverables/test-cases/
- adhoc: https://qatestlab.com/resources/knowledge-center/ad-hoc-testing/
- Why Configuration Testing?: https://blog.qatestlab.com/2015/08/05/why-configuration-testing/
- Regression and Confirmation testing. What is the difference?: https://blog.qatestlab.com/2011/11/08/regression-and-confirmation-testing-what-is-the-difference/
Source URL: https://blog.qatestlab.com/2011/10/26/configuration-management-in-software-testing/