7. What is configuration management?
Configuration
management is the detailed recording and updating of information for
hardware and software components. When we say components we not only
mean source code. It can be tracking of changes for software documents
such as requirement, design, test cases, etc.
When changes are done in adhoc and in an uncontrolled manner chaotic situations can arise and more defects injected. So whenever changes are done it should be done in a controlled fashion and with proper versioning. At any moment of time we should be able to revert back to the old version. The main intention of configuration management is to track our changes if we have issues with the current system. Configuration management is done using baselines.
When changes are done in adhoc and in an uncontrolled manner chaotic situations can arise and more defects injected. So whenever changes are done it should be done in a controlled fashion and with proper versioning. At any moment of time we should be able to revert back to the old version. The main intention of configuration management is to track our changes if we have issues with the current system. Configuration management is done using baselines.
8. How does a coverage tool work?
While
doing testing on the actual product, the code coverage testing tool is
run simultaneously. While the testing is going on, the code coverage
tool monitors the executed statements of the source code. When the final
testing is completed we get a complete report of the pending statements
and also get the coverage percentage.
