ST Management Usually Make Team Leaders Confused: What Is St Management? This Paper Offers A Beneficial Solution To these Questions.
Software test management
(嫦娥 Engineering Ground Application System Software Quality Dai Jinlong)
Summary:
For a long time, the test management is in a very low level, and the emergence of automated test management tools gives people misunderstandings. It seems that test management is a simple styled work. This paper discusses the general composition of the software test management discipline in the idea of the author and the specific content of each component. The author believes that test management has an important guiding role in the implementation of software testing technology, and has a guaranteed and promotion of test team construction, which is a part of modern software project management that cannot be ignored.
Keywords: Software Test Management Team Organizational Management Test Plan Management Defect (Error) Track Management Tester Management
Copyright statement: This papers are copyrighted by Dai Jinlong. Any substantial reference or reprint is required to indicate copyright matters and consent to the author.
Software Test Management The topic to be resolved is how to ensure that software test technology can be implemented smoothly in software projects, and produce expected results. According to the object of management, software testing is roughly divided into software test team organization management, software test plan management, software defects (errors), and software test parts management. The following is an overview of the contents of these four parts.
The software test team organizes how often is how the test team should form. In actual project development, we often see some units of ignore the meaning of the test team. When you want to implement test, you often find a few programmers to act as testers; some units understand the importance of forming the test team, but In the specific implementation, there are often some new business new doors who have no development experience to do test work, which often leads to the low test efficiency, and testers have tasted the test work. A good test team must first take the leader, he must have an extremely rich development experience, and it is a chest for the disadvantages or mistakes in the development process. In addition, he should have affinity and personality. Second, the test team should have a member of a long manner, such as the use of certain automated test tools, or to write automated test scripts. In addition, the test team should have part-time members. For example, in the implementation of the test, peer review is the most common form of use, these peer experts are the scope of part-time test team members. There are often no shortcomings for the lack of experience software in the test team, and this part can arrange to work in delivery verification or black box testing.
Software test plan management is popular in arranging test processes. This part of the content covers several parts of software test planning, software testing technology, testing progress management, and cost management. The test planning work mainly refers to the implementation of planning work before the implementation of specific test activities, such as drafting test outline and test plan; software test technology tailoring work mainly means that the test team should have the test technology to be implemented according to the specific actual number of software projects; Test progress management is mainly referring to the time schedule of the discharge test, and should be adjusted accordingly if there is any change; the content of the test cost management will open the resource requirements involved in the test activity.
Software Defects (Errors) Tracking management is popular to ensure that the defects (errors) have been developed or processed without introducing new defects (errors). Specifically, when the test team discovers the defects or errors in the document or code through a variety of ways, it is not a test report to step on the grass, but will continue to urge the development team in time to close known defects in time after submitting the report. Or errors (of course, if necessary, if you have to deal with these defects, the error is sorted in sequence so that the development team can easily schedule the sequence of processing. When the development team closed the defects in the test report (errors), the test team also needs to verify that the development team has introduced new errors during the closing process. Usually, this process is called the regression test. Return test If the problem is found, continue to report the development group, cycle according to the above flow until the regression test is finally passed. Software test parts management is popular to guide the construction of a wealth library of test teams and conduct skills training for test team members to help them use this wealth library. Here, the wealth library refers to a software test piece. Test Parts (Testware) is an uncommon word, which includes lessons learned, test techniques, test tools, specifications, and some modifications, test techniques, test tools, specifications, and some modifications. Can be extended to a generic test script program. The better the test parts management work, the less the test team can take less detours during the actual test, the more fully intellectual communication and delivery of the team, the repeated development of the test script or specification document can be effectively avoid. Software test parts management work includes two parts, one is construction, the other is training. The construction work is to collect all kinds of test external documents, test tools, test scripts, including conferences, summary reports, technical experience, etc., collecting testing testers. The training work is in the form of a technical lecture, a formal or informal team meeting, issued by learning materials.
The content of the software test management discipline is made from the software test team to organize management, software test plan management, software defects (error) tracking management, and software test parts management. What needs to be pointed out is that the software test management discipline is still in a non-mature development period, and the discussion of the author has made everything we can, but it does not guarantee that the software test management has been covered. The right is to throw the jade, please read the readers and friends a lot of criticism.
references:
1 Paul C.Jorgensen, software test (method of practitioners), Machinery Industry Press. 2003, 7
2 Edward Kit, Software Test Process Improvement, Machinery Industry Press, CITIC Publishing House. 2003, 4
3 Standards Writing Group, Space Software Engineering Implementation Technical Guidelines and Examples, Trial of the Five Courtes. 2003, 4
About the Author:
Dai Jinlong, currently in national major projects
The work quality management of the ground application system is served in the project. Software project coding and testing work in Java has deep experience and practical experience. In the early years, I focus on the development of scripting languages, and now I am interested in software testing and Java. Hobbow mountain, Qigong. You can contact him through popodai@163.com.
