Chapter 7 Software Testing Project Management

---

---

foreword

Software testing is an important part of software engineering and an important means to ensure software quality. With the increasing complexity of software and the continuous development of the software industry, software testing has received more and more attention. This chapter will introduce and discuss the basic characteristics of software testing projects, ideas, basic principles, methods and techniques of project management.

---

1. Overview of software testing project management

1. Software testing project and software testing project management

1. Test project
   The test project is a phased task to complete a specific test target for a specific software in a certain organization using limited human and financial resources under a specified environment and requirements. The task should meet certain quality, quantity and requirements. Technical indicators and other requirements. Test items generally have the following basic characteristics.
   (1) The uniqueness of the project
   (2) The organization of the project
   (3) The life cycle of the test project
   (4) The resource consumption characteristics of the test project
   (5) The goal conflict of the test project
   (6) Intellect-intensive and labor-intensive Features
   (7) Uncertainty factors in test item results

2. Test project management
   Test project management is to take the test project as the management object, through a temporary special test organization, use special software test knowledge, skills, tools and methods to plan, organize, execute and control the test project, and Analyze and manage activities in terms of time cost, software testing quality, etc. Test project management runs through the life cycle of the entire test project, and manages the entire process of the test project.

   Test project management has the following basic characteristics.

   (1) The idea of ​​system engineering runs through the whole process of test project management
   (2) The organization of test project management has certain particularities
   (3) Create and maintain an environment for the smooth progress of test work
   (4) The method of test project management, Advanced tools and techniques

3. The basic principles of test project management
   (1) Always be able to put quality first
   (2) Reliable requirements
   (3) Try to set aside enough time
   (4) Pay enough attention to test planning
   (5) Properly introduce test automation or Test tools
   (6) Establish an independent test environment
   (7) General project management principles
   General project management principles include smooth and effective communication, consistency and timeliness of documents, and project risk management.

2. Scope management of software testing projects

Test project scope management is to define all the work that must be included in the project and only need to be included, and guide other test project management work to ensure the smooth completion of the test work.

2. Software testing documents

1. The role of software testing documents

(1) Facilitate communication among project team members
(2) Facilitate the management of the test project
(3) Determine the effectiveness of the test
(4) Verify test resources
(5) Define the risk of the task
(6) Evaluate the test results
(7) ) to facilitate retesting
(8) to verify the correctness of requirements

2. Types of software testing documents

According to the different functions played by test documents, it is usually divided into two categories, namely pre-work documents and post-work documents. The documents of test plan and test cases are pre-work documents. The test plan specifies the requirements of the test in detail, including the purpose, content, methods, steps of the test, and the criteria for evaluating the test. Since the content to be tested may involve software requirements and software design, the writing of the test plan must be started as early as possible, and the writing of the test plan should start from the requirements analysis stage.

According to different methods of test documentation preparation, it has two kinds of manual preparation and automatic preparation. The so-called automatic compilation is characterized in that the compilation process is supported by document compilation software, and the compiled document can be recorded on a machine-readable medium. With the help of powerful tools and means, it is easier to complete information search, comparison, modification and other operations. Various commonly used text editing software can be used to prepare test documents.

3. Main software testing documents

(1) Software test document
(2) Test plan template
(3) Test design specification
(4) Software test case specification document template
(5) Test procedure
(6) Test log
(7) Software defect report
(8) Test summary Report

3. Organization and personnel management of software testing

1. Overview of organization and personnel management of software testing

The tasks of test organization and personnel management are as follows.
• Choose an appropriate organizational model for the test project.
• Determine the organizational form within the project team.
• Reasonable allocation of personnel, clear division of labor and responsibilities.
• Effectively manage the thoughts, psychology and behavior of project members, give full play to their subjective initiative, and make them closely cooperate to realize the project goals.

2. Organizational structure of software testers

At present, the common test organization structure has two forms : independent test team and integrated test team .

3. Software Tester

The competence of testers should include the following items.
• General competencies: including expression, communication, coordination, management, quality awareness, process approach, software engineering, etc.
• Testing skills and methods: including testing basic concepts and methods, testing tools and environment, professional testing standards, job performance evaluation, etc.
• Test planning capability: including risk analysis and prevention, formulation of software release/acceptance criteria, test objectives and plans, test plan and design review methods, etc.
• Test execution capabilities: including test data/scripts/use cases, test comparison and analysis, defect recording and processing, and automation tools.
• Test analysis, reporting and improvement capabilities: including test metrics, statistical techniques, test reporting, process monitoring and continuous improvement.

4. Communication methods of software testers

There are mainly the following:
• Formal impersonal means, such as formal meetings.
• Formal inter-personal communications, such as formal discussions among members, etc. (generally do not lead to resolutions).
• Informal inter-personal communication, such as free communication between individuals. • Electronic communication, such as E-mail (e-mail), BBS (electronic bulletin board system), etc.
• Networking of members, such as members interacting with experienced stakeholders outside the group or outside the company.

5. Incentive mechanism for software tester management

As a tester, the 7 principles of efficiency in testing artifacts are as follows.
• Think proactively and act proactively.
• Start with the goal in mind so you don't get lost.
• Putting important things first (but often putting urgent things first).
• Understand people first, then be understood.
• Seek a win-win situation.
• Cooperate with each other and pursue 1+1>2.
• Lifelong learning, self-renewal and continuous improvement.

6. Training of software testers

Software testing training mainly includes the following training content.
• Test basic knowledge and skills training.
• Test design training, test tool training.
• Test object—software product training.
• Testing process training.
• Test management training.

7. Risk management in software testing organization and personnel management

4. Software testing process management

1. Tracking and quality control of software projects

Software testing, like software development, follows the principles of software engineering and has its own life cycle. Software test process management is based on the widely adopted V-model, which supports any phase of the system test cycle. Based on the V model, the left side is design and analysis, which is the process of software design and implementation, accompanied by quality assurance activities—the review process, that is, the static testing process; the right side is the verification of the results on the left, which is the process of dynamic testing, namely Test the results of the design and analysis to confirm that the user's needs are met. Each phase in the software development cycle has an associated testing phase.

2. Process management of software testing projects

(1) Test project initiation
(2) Test planning phase
(3) Test design phase
(4) Test execution phase
(5) Review and analysis of test results

5. Configuration management of software testing

In general, software test configuration management includes the following five most basic activities.
• Configuration ID.
• version control.
• Change control.
• Configuration status reporting.
• Configuration auditing.

6. Software testing risk management

Risk analysis is the process of identifying and evaluating potential problems, ie prioritizing what to test. Risk analysis includes the following two parts.
• Likelihood of Occurrence: How likely is the problem to occur?
• Severity of impact: What are the consequences if the problem occurs?

Usually risk analysis adopts two methods: tabular analysis method and matrix analysis method . A general risk analysis form includes the following items.
• Risk ID: Indicates the unique ID of a risk event.
• Risk issue: A brief description of the occurrence of the risk issue.
• Likelihood of Occurrence: The level (1-10) of the risk's likelihood of occurrence.
• Severity of Impact: Scale (1-10) of the severity of the risk's impact.
• Risk Prediction: The product of the likelihood of a risk occurring and the severity of its impact.
• Risk Priority: Ranking of risk predictions from high to low

There are two basic contents of risk management: risk assessment and risk control .

7. Cost management of software testing

1. Overview of software testing cost management

The process of cost management includes the following aspects.
• Resource planning: includes deciding what resources (personnel, equipment, and supplies) and the amount of each resource will be used to implement the software testing project. Its main output is a list of resource requirements.
• Cost Estimates: Include an approximate estimate of the cost of resources required to complete the software testing project. Its main output is the cost management plan.
• Cost Estimates: Includes allocation of overall cost estimates to individual jobs to establish a baseline plan against which to measure performance. Its main output is the cost baseline plan.
• Cost control: includes controlling changes in the software testing project budget, its main outputs are revised cost estimates, updated budgets, corrective actions and lessons learned.

2. Some basic concepts of software testing cost management

1. Test Fee Validity
2. Test cost control
3. cost of quality
4. Defect detection rate

3. Basic principles and measures of software testing cost management

1. Principles of software testing project cost control
   (1) Adhere to the principle of cost minimization
   (2) Adhere to the principle of comprehensive cost control
   (3) Adhere to the principle of dynamic control (4)
   Adhere to the principle of project target management
   (5) Adhere to the combination of responsibility, power and benefit in principle

2. Software testing project cost control measures
   (1) organizational measures
   (2) technical measures
   (3) economic measures

---

Summarize

The above is what I will talk about today. This article only briefly introduces the basic concepts of software testing. I hope it can be helpful to you who are reading. If you are also interested in software testing, just follow me to learn.

If you think my writing is not bad, please give me more likes and encouragement. Your support is also the biggest motivation for me to keep moving forward. At the same time, you are welcome to share this article with your friends and learn together. Finally, everyone is welcome to discuss with me the problems encountered in the learning process in private messages and comments, so that everyone can make progress together.