How to establish a software testing management system?

How to establish a software testing management system?
Software testing is a key step in software quality assurance. The research results of the American Institute of Quality Assurance on software testing show that the earlier problems in the software are found, the lower the development cost; the cost of fixing software defects after coding is 10 times that before coding, and fixing software defects after product delivery The cost of the software is 10 times that before delivery; the higher the software quality, the lower the maintenance cost after the software is released. In addition, according to the statistics of internationally renowned IT companies, their software testing costs account for more than 50% of all research and development costs of the entire software engineering.
In contrast, there is still a big gap between Chinese software companies and international standards in software testing. First of all, in terms of understanding, focusing on development and ignoring testing, failing to realize that the on-time completion of software projects depends not only on developers, but also on testers; secondly, management is casual and simple, and an effective and standardized software testing management system is not established. ; In addition, lack of the support of automation tools, most companies do not use software test management systems in software testing. Therefore, for domestic software companies, not only should they improve their understanding of software testing, but also establish a sound software testing management system. The main purpose of establishing a
software testing management system is to ensure that software testing plays a key role in software quality assurance: monitoring and measurement of software products The characteristics of software products are monitored and measured, mainly based on software requirements specifications Instructions to verify that the product meets the requirements. Whether the developed software product can be delivered, the quality indicators must be set in advance and tested. Identification and control of products that do not meet requirements For software defects found in software testing, their attributes and treatment measures should be carefully recorded and tracked until they are finally resolved. After eliminating software defects, it is necessary to verify again. The verification of product design and development verifies the requirements analysis, software design, and program code by designing test cases to ensure that the program code is consistent with the software design specification, and the software design specification is consistent with the requirements specification. For the unqualified phenomenon found in the verification, it should also be carefully recorded and dealt with, and tracked and solved. Once resolved, verify again.




Monitoring and measurement of software process A large amount of data and information about software process and its results can be obtained from software testing, which can be used to judge the effectiveness of these processes and provide decision-making basis for the normal operation and continuous improvement of software process.
Establishing a test management system
Generally , the process method and the system method are used to establish a software test management system, that is, the test management is regarded as a system, and the various processes that make up the system are identified and managed to achieve the set system goals. At the same time, these processes should be synergistic and promote each other, so that their overall effect is greater than the sum of the functions of each process. Its main goal is to find and eliminate software defects as much as possible under the set conditions. The test system is mainly composed of the following six interrelated and interactive processes:
1. Test planning
Determine the goals and strategies of each test phase. This process will output the test plan, define the test activities to be completed, evaluate the time and resources required to complete the activities, design the test organization and post authority, arrange activities and allocate resources, and arrange activities to track and control the test process.
Test planning is carried out in parallel with software development activities. During the requirements analysis phase, an acceptance test plan is completed and submitted for review along with the requirements specification. Similarly, in the outline design phase, the system test plan is completed and reviewed; in the detailed design phase, the integration test plan is completed and reviewed; in the coding implementation phase, the unit test plan is completed and reviewed. For revised parts of the test plan, a re-review is required.
2. Test design Design the test plan
according to the test plan. The output of the test design process is the test cases used in each test phase. Test design is also carried out in parallel with software development activities, and the results can be submitted for review as an annex to the test plan for each phase. Another aspect of test design is regression test design, which is to determine the set of use cases for regression testing. Re-review is also required for the revised part of the test case.
3. Test implementation
Use the test case to run the program, compare and analyze the obtained operation results with the expected results, record, track and manage software defects, and finally get the test report.
4. Configuration management
Test configuration management is a subset of software configuration management that acts on all phases of testing. Its management objects include test plans, test solutions (use cases), test versions, test tools and environments, and test results.
5. Resource management
Including the management of human resources and workplaces, as well as related facilities and technical support. If testing labs are established, there are other management issues.
6. Test management
Use appropriate methods to monitor the above process and results, and measure when applicable to ensure the effectiveness of the above process. If the intended results are not achieved, appropriate adjustments or corrections should be made.
In addition, the test system and the software modification process are interrelated and interactive. The output of the test system (software defect report) is the input for software modification. In turn, the output of the software modification (the new test version) becomes the input to the test system.
According to the above 6 processes, 6 steps to establish a software test management system can be determined:
identify the processes required for software testing and their applications, namely test planning, test design, test implementation, configuration management, resource management and test management;
determine these The sequence and interaction of processes, the output of the former process is the input of the latter process. Among them, configuration management and resource management are the supporting processes of these processes, and test management is to monitor, test and manage other test processes;
to determine the criteria and methods required for these processes, generally develop procedures for documenting these processes, and Criteria and methods for monitoring, measuring and controlling;
ensuring that necessary resources and information are available to support the operation and monitoring of these processes;
monitoring, measuring and analyzing these processes; and
implementing necessary improvements.
TestCenter builds a test management system
The so-called workers want to do good things, they must first sharpen their tools. With tools that can do more with less, work efficiency can naturally be improved. The software testing management system is a sharp tool to establish a software testing management system and ensure the smooth progress of software testing. TestCenter is a software test management system developed by SPASVO company from the needs of software testing and in accordance with international quality management standards.
It adopts B/S structure and can be installed on a Web server. Project related personnel can log in and use TestCenter at the same time through the Internet in different places to complete software testing collaboratively, which can reduce the cost of business trips for centralized personnel. It also provides corresponding automation functions, which can efficiently write, query and reference test cases, and quickly fill in, modify and query software defect reports, reducing human input. It comes with a test case database and a software defect database, which can help project members better implement software testing.
In specific software defects, it divides its life cycle into 6 life states: open, working, verify, cancel, close and defer, which can record, track and manage the life process of each software defect in detail until the defect is eliminated. . It also sets attributes such as severity level, priority, defect type, etc. for software defects, can automatically distinguish the priority of software defects, and can provide relevant analysis and statistical functions.
In addition, in addition to monitoring and analyzing software quality, TestCenter can automatically count the progress of programmers and testers. The test document template it provides can transfer test documents and data directly to Office, making operations such as typesetting and printing more convenient.
TestCenter (TC for short) is a test life cycle management tool for the test process. The test process in line with the TMMI standard can quickly establish a complete test system, standardize the test process, improve the test efficiency and quality, realize the process management of the test, and improve the test process. Productivity of Engineering.
TestCenter test management tool official website: http://www.spasvo.com.cn/products/tc.asp