Configuration Management and Software Testing
Configuration management
Configuration management identifies software configurations at different time points in the software life cycle and systematically controls changes to these identified software configuration items, so as to ensure the integrity and traceability of software products the process of.
SCM (Software Configuration Management), a CM dedicated to software configuration management.
SCM application, including in the initial stages of development and all maintenance stages of the product.
Compared with CM, SCM has two characteristics: software is easier to manage than hardware, and SCM has automation potential.
Configuration management role
1 Can effectively manage the changes of documents, codes, etc. in the project;
2 to easily reproduce the historical version of a file;
3 It is convenient to recompile a historical version
4 Multi-team development and parallel development in different places
5Improve the work efficiency of the project team when people move
The main body of configuration management work includes: planning, identification, change control, configuration status reporting, configuration auditing
configuration plan
Plan: define or refer to the steps and moves that describe how configuration and change control management is to be performed in software product development
Configuration ID
Identification includes software configuration items, software configuration baselines, identification of controlled libraries
The objects used include: system specifications, software requirements specifications, design specifications, source codes, test specifications and other artifacts generated in the software development process.
The software configuration management library is divided into:
Development library: information to be retained in the development process, for developers to use;
Controlled library: At the end of a certain stage of development, the artifact product is stored or the relevant information is stored;
Product library: After the system test is completed, the final product is stored in the library, waiting for delivery or installation;
Software controlled library identification includes the following:
<1 storage location;
<2 storage media
<3 The number of homologous libraries and the maintenance mechanism of parallel content
<4 Contents of software configuration items
<5 Contents of software configuration status
<6 Conditions for entering software configuration items, including minimum state compatible with controlled libraries
<7 Measures to prevent intentional or accidental damage and degradation, and effective recovery procedures
<8 Conditions for detecting configuration items
<9 Access settings for people and groups with different permissions
change configuration
For the identified configuration items, change control should be strictly implemented, including check-in and check-out control, change control, version control and access control.
Configuration Status Report
Document the identification and configuration of each new and changed software configuration. When a software configuration item is brought into configuration control, the SCM process shall maintain version and status at each improvement, record and report the status and approved status of change requests. Change the implementation status and check if the change is justified.
Configure Audit
Check whether the configuration procedures are complete
Check if the change is complete
Verify that the current baseline is traceable to the previous baseline
Confirm whether each SCI correctly reflects the needs
Ensure the validity of SCI and media, and regularly back up to prevent accidents
Version control and software testing, the correct change process can let the tester know the scope of the change at the first time, so as to formulate the corresponding regression testing strategy.