Test those things in the project process

foreword

As a part of the whole project, testing plays an indispensable role in the project process. Some teams lack the role of project management. At this time, testing is particularly important to the promotion of the project process and the assurance of project quality. A good test can do a good job in project management and timely risk warning from the perspective of QA in the entire project process, so that the project can be launched on schedule and ensure the quality. The industry has always emphasized the pre-testing, so in the project, how to do the pre-work according to the project situation to promote the project process, so that everyone can work happily? This article takes my own project team as an example to describe some things in the project process, and I hope to discuss with you~

1. The role of QA in the project

[why] Clarify what the goal is: make clear what the goal of this project is, and make some adjustments according to the goal, such as demand realization, project quality, research and development time point, etc.

[when] the deadline of the project: Considering the particularity of the project team, we need to know when the project needs to go online, clarify the project deadline, and formulate an appropriate test plan according to the time node

[what] What do we need to do at each stage: we can focus on the QA participation and output in the project process. There is input to have output, so the output link is often where QA spends time thinking.

[how] What to do when encountering risk points: In the testing phase, in addition to the risk points in the QA link that need to be exposed and pushed in time, research and development and products are also doing some work at this stage. In project process management, as the most downstream participant, you need to pay attention to these risk points, expose and push solutions in time.

【who】QA、RD、PM

2. The challenges we face

2.1 Challenge points

1. The frequency of releases ranks second. In 2021, there will be 71 releases throughout the year, which is equivalent to one version being iterated every week. The rhythm of rapid iteration requires high human efficiency and team collaboration efficiency.

2. Throughout 2021, the number of bugs per capita in R&D is 123, with many bugs and low quality of testing. In order not to prolong the project cycle, it is very important to ensure a short bugfix time, and at the same time, we must consider how to improve the quality of the test.

3. Throughout 2021, testers will raise the most bugs per capita. In the case of a tight project rhythm, the efficiency of finding and raising bugs must be improved.

2.2 About the quality of the test

For the content of the above challenges, we can see that we have shortcomings in the quality of the test. We have tried to increase the proportion of smoking use cases, cross-execution of smoking, and time estimation to increase the smoking time. Finally, we found that the effect of the harvest was limited. The main reasons are as follows:

1. Multi-party cooperation and the project has a fixed deadline: Due to the particularity of the project, some of the requirements are multi-party cooperation mode and there is a fixed deadline, so the project needs to be launched as soon as possible. In the case of extremely high requirements for project efficiency, we allow some levels of depth. If the bug is online, do hot for the online situation
   fix。
2. The rhythm of the project is tense and it needs to be updated quickly: the existing R&D team is a serial rhythm, which can continuously and efficiently iterate. In order to ensure the stability of the project rhythm and avoid the rhythm disorder caused by the excessively long project cycle, we accept step-by-step In the form of the test, it is possible that the smoking function is not complete, resulting in the quality of the test being not as good as expected.

Based on the above reasons, we can see that when we need to make a certain choice between quality and efficiency, we need to lean towards project efficiency. Therefore, since we cannot better change the quality of the test, we should change what we can.

3. Faced with these challenges, what can QA do

What can QA do to make the entire iteration cycle shorter, and to iterate quickly and with fewer online problems when there are many bugs? Let's take a look at our project process:

From the perspective of the entire project process, it may be the same as many teams. In the process, QA is a part of the downstream. It can be seen that QA participates in the output of a lot of content. These parts are the points we can try to improve.
So let's see from these outputs, what changes have been made by QA in the face of the above challenges and what difficulties are there.

3.1 Project schedule

Project Schedule Template:

[when] The project schedule is generally after the requirement review is completed, and the requirement module and the development module are split according to the requirements.
In scheduling, QA's work: familiarize with requirements, split requirement modules, and develop test plans
QA students join the module disassembly to better understand the requirements. The divided development module can also quickly know which end the bug belongs to when there is a bug, and which corresponding developer should be referred to.
According to the test time and general development cycle of each module, QA students can also formulate corresponding test plans.

【what】-- What exactly needs to be done by QA

1. Assist in the development of split function modules to ensure that the modules have corresponding development leaders
2. Confirm the project deadline, total estimated development time and test time

3.2 Test plan development

Project Test Plan Template:

[when] The test plan is generally provided within 1 day after the project schedule is given, and will be dynamically adjusted according to the schedule.

In the test plan, QA's work: estimate time and manpower according to requirements, clarify the test environment and strategy, formulate a reasonable test plan, and estimate risks

【what】-- What exactly needs to be done by QA

1. Split the functional modules, and the modules clearly define the corresponding tests. (Including use case writing arrangement, first and second round testing arrangement and compatibility testing arrangement)

2. Estimate the overall test time of the project and the test time of each round

3. When the first round is nearing the end, the pre-release time should be clarified with the development; when the second round is nearing the end, the development time should be clarified with the development of the online environment

4. If there are data configuration items, before the start of the second round of testing, clarify the required content and completion time with the product.

The above points 1 and 2 are provided as soon as possible, and the rest can be given at the corresponding time point. Of course, in case of changes in demand, changes in manpower, etc., it needs to be proposed and adjusted in time.

【how】-- How to do it

According to the development schedule, dynamically formulate and adjust a reasonable test plan.

• According to the test time, determine the execution order and allocation of use cases:
  In the test plan split as shown in the figure below, the background configuration (Spark) is inconsistent with the user-end test time. Combining the two test time points, we use the time before the user-end test to execute the use case of the background configuration first, so that even if the test is divided Step by step test, we can also ensure that the test resources can keep up with each test.
  
• Develop testing rounds based on features
  For the main function: the test cases need to be executed multiple times. Generally, three rounds of testing are formulated, one in the test environment, two in the pre-release environment, and three in the online environment.
  For internal functions that do not affect the use of users: formulate a round of testing, and test a round in the test environment. For example, the configuration background such as Spark is for operation, do a round of testing, after pre-release, product walkthrough verification + configuration content can be
  The function of the activity class: According to the complexity of the activity and the frequency of use, the test rounds are formulated. For example, the New Year's event is a one-time event and the event time is tight. After the evaluation, we did a round of testing in advance and went live, and the quality of the launch is also good. Specific test process: try the activity test process
  
• According to the module, use case volume and difficulty division, set the daily use case execution goal for each person
  A round of test module division is divided according to use case writing and familiarity
• Implement cross-testing to avoid omissions or inefficiencies due to unfamiliarity
  The two rounds of testing are crossed. Using the task assignment of the TC platform, you can also clearly see the number of tasks and the completion of the team members.

As shown in the figure below, the dismantling of the test plan and the allocation of personnel are carefully divided into the daily work goals of each person, and the allocation of each module will be crossed. One round of testers finds that the use cases are imperfect or inconvenient to test, even if they provide Documentation so that the second-round personnel can get started with the test as soon as possible.

[Summary]: We can see that there are four ways to adjust the test plan, the main purpose is to use these methods to complete the test task more efficiently, to ensure that the project is launched on schedule; to find bugs more comprehensively and comprehensively, and improve the quality of the project . Reasonable adjustment and distribution of the test plan is one of the effective ways to face various challenges in the project process.

3.3jira customization process

1. Customized jira project process:
   

Version release management trilogy:

• Jira version release management: From the establishment of the product version to the final review, the entire process and data statistics are reflected in the jira dashboard, which is convenient for unified management
• Automatic synchronization of project progress: as follows, the project team members can clearly know the current project progress, and the version progress will be automatically synchronized in the large group every day; the completed project will also automatically synchronize the review information according to the project situation
  

【summary】:

1. The customized process makes the process more unified, standardized and intelligent.

2. The timely synchronization of key information can reduce repeated meetings such as daily stand-up meetings and information synchronization meetings, saving time.
The previous collaboration between the teams is smoother, and the team collaboration efficiency and human effectiveness can naturally be further improved.

2. Tips for QA to efficiently improve bugs and develop fast bug fixes:

2021Q1 In the discussion on the collection and efficiency improvement of efficiency tools, the optimization suggestions for the bug raising process have been implemented one by one, and the speed of everyone raising bugs has been greatly improved. The main summary is as follows:

• Bugs distinguish problem types - make bug classification more accurate, better analyze data, and push corresponding personnel
• Bug status display optimization - each status is clear at a glance, and you can find the bugs that need to be dealt with faster
• Bug description preset version, steps, equipment and other information - reduce repeated content input, more efficient bug

• Jira mobile version access and use - attachment content is more convenient to upload, bug description is more accurate, and repeated communication costs caused by unreproducible, unclear description and other reasons are reduced
  
• The bug process is newly added: a round of missed testing, the option to fix bugs, and the state of unclear descriptions of bugs - of course, the purpose of these indicators is not to investigate the responsibility of development or testing, but to analyze bugs, summarize the reasons, and find out the deficiencies. Where there is a problem (such as imperfect use case design, development and repair of bugs without self-testing, etc.), everyone can make progress together to improve the quality of the project, so that the project can be carried out more smoothly and efficiently.
• Automatically remind the development of QAfix and acceptance bugs: —— Accurately find the bugs that need to be dealt with, and the processing efficiency is greatly improved
  During the review of the project process, we agreed that p1bug needs to be fixed on the same day, p2bug in principle, the fix cycle does not exceed T+1 days, and the acceptance does not exceed T+2 days. As shown in the figure below, the content of R&D and testing is automatically reminded according to the formed specifications:
  
  

【summary】:

1. Even some preset bug-reporting information and interface optimization make the test work more "elegantly", and bug-reporting and bug-checking are more energetic.

2. The agreement and message push of the T+1 repair cycle give R&D a mental expectation. Just as we adjust the testing strategy according to the project situation, R&D also adjusts the working mode according to the expectations we give, so that the R&D fix bug cycle can be guaranteed to Shortest, efficient and quality bug fixes.

The adjustment of the workflow and the full expectation of blessing greatly improved the work efficiency of the entire team.

3.4 Test report

1. Test Daily

[when] After the general project is tested, a daily report needs to be sent before get off work every day

【what】-- What exactly needs to be done by QA

Summarize the progress of other QAs, and send daily or weekly reports according to the project situation.
The risk item in the daily report can be modified according to the project situation, and the synchronization plan, reminder items, etc. can be written.
Push development to fix bugs: The repair cycle of p1 does not exceed T+1 days. When the number of bugs is large, the development and revision can be appropriately urged according to the test situation (for example, one round of testing is nearing the end, and there are still many front-end bugs on the server side, so it needs to be urged)

【how】-- How to do it

On the galaxy platform tool, an automatic daily report generation tool is implemented, which can automatically generate the daily report content every day, so that everyone can see the progress, and the current bug status and links are also included in the daily report, so that research and development can find their own bugs faster.
The effect of one-click generation of the daily report is as follows:

【summary】:

The automatic generation of the daily report saves the time of daily summary progress of the test, and directly and greatly reduces the communication and synchronization cost of key information, which is another buff for the improvement of human efficiency and team collaboration efficiency.

2. Quality Report (Test Report)

[when] After the project is launched, summarize and sort out the project

【how】-- How to do it
Combined with the use process of jira, test reports can be generated with one click and the quality platform can be synchronized.

Example of generated test report:

3.5 Project review

[when] Within a week after the project is launched, small projects can merge organizations if necessary

[why] The purpose of the review: to discuss the countermeasures for the deficiencies in the project, and strive to do better next time

【what】-- What exactly needs to be done by QA

1. Data document preparation: The form is actually not limited. The required data and documents can be prepared, or they can be organized in turn with the development.

2. The todo list formed at the meeting needs to be followed up

【how】-- How to do it

Restoration example:

Jira kanban for re-examination and improvement: as shown below—ps: It can also be used when urging bugs or sending daily newspapers, which is relatively clear

[Summary]: Regularly do project review, let the team realize our current problems, and promote the project process to do better every time.

【insufficient】:
Of course, during the review process, although the teams reached some consensus to improve together, they also encountered a series of problems.

Question 1: When the rhythm of the project is already very tense, everyone may be catching up with the project schedule and have no spare time to do the review and summary work, pursuing efficiency and ignoring quality.

Question 2: The todolist formed by the review does not have time to follow up, which leads to the conclusion of the review and the final content of the review, and the review is meaningless.

Question 3: Some review and improvement points are often not implemented according to regulations due to various special reasons.

Based on the above reasons, the effect of re-stocking and harvesting is relatively limited, and it is also a proposition that we need to discuss and improve in the future.

4. Project Risk

4.1 Risk Assessment

In the project process, we pay attention to what needs to be done at each stage, and also do project management and control, pay attention to project risks, and keep deadlines.

Risks can be divided into two categories: quality risks and schedule risks

for example:
The time for writing use cases is not enough, which affects the testing time and launch time, which is called schedule risk; while when writing use cases, the people who write use cases are not familiar with the function, and the use case coverage is insufficient, which can be called quality risk.

Here we mainly focus on the project progress, so we focus on the progress risk. Schedule risk is the risk that occurs in the project schedule and thus affects the time point of the entire project.

In the test meter, we have designed the risk column to be the first, the purpose is to allow QA to observe and record risks from the perspective of testing in a timely manner in the project process.

for example:

4.2 Risk Countermeasures

When faced with risks, a case by case discussion is required. When a schedule risk arises, the first principle is to expose the risk in a timely manner and find a way to reduce the risk as much as possible.

Many projects of the project team cooperate with other departments, have fixed deadlines and allow some known problems to be brought online, so we generally discuss solutions from the perspective of test development as follows:

If the above plan cannot keep the deadline, it is necessary to consider the project extension.

Epilogue

The above content is the author's project team combined with the existing testing process to promote the process and the summary introduction after the promotion according to the challenges encountered by the project.
In view of the particularity and differences of different project groups, the methods and means mentioned in this article may only be the tip of the iceberg and may not be fully applicable to various projects. It is actually a big proposition to do pre-work according to the project situation to advance the project process. Different project teams sometimes have different problems. To test what more nice things can be done in the project process, we still need to rely on everyone. Explore and summarize the current situation. You are also welcome to leave a message to discuss with us~