1.Background
-
With the rapid iteration of the business, the proportion of development self-test requirements and QA test requirements is equivalent. We cannot control the quality of the development self-test requirements. And as the self-test requirements increase, QA's familiarity with the business will also increase. A fault occurs;
-
Some businesses have stabilized as a whole, with fewer iterations, but some historical issues occasionally appear online, causing operations students to find development students to deal with them temporarily when using related functions;
-
As the volume of business orders continues to increase, we are paying more and more attention to NPS. Experience-related issues will seriously affect the user experience and lower NPS, while a good interactive experience is more conducive to improving NPS and retaining users;
Based on the above problems, we will regularly organize development students to conduct business inspections together. We hope to solve these problems through business inspections, improve the availability of the system, and reduce online problems; through inspections, everyone can understand the business from the user's perspective. , experience the business, thereby improving user experience; finally, I also hope that through inspections, we can improve everyone’s quality awareness, and everyone will be jointly responsible for quality!
2. Inspection method
Before organizing the inspection, we have been thinking about two questions, that is, how to make everyone more actively participate in the inspection and how to improve the efficiency of the inspection? As the saying goes, what suits you is the best. In the end, we decided to organize different forms of inspections based on different business characteristics. Therefore, before introducing the inspection method, I will briefly introduce the two businesses that I am responsible for. They will be referred to as business A and business B below.
2.1.A business
1) Business process
2) Business characteristics
The business process is relatively simple and simple, and there are many front-end interactive functions.
3) Business status
The overall business has stabilized, mainly focusing on operations, with relatively few project iterations and minor changes in overall functions.
2.2.B business
1) Business process
3) Business characteristics
The process is complex and diverse, and each branch has separate business logic.
4) Business status
The business is in a rapid development stage, with short iteration cycles and frequent functional changes.
In summary, according to the business characteristics of the two, considering that the business process of A is relatively simple, and the case sometimes limits everyone's thinking, it was finally decided to adopt a free inspection method, which can better simulate the user's usage habits and discover question. Business process B is relatively complex. Free inspections may not cover the entire process, so we ultimately adopt the method of providing cases to guide everyone to cover as many scenarios as possible, so that we can better identify problems from a business perspective.
3. Points of concern
This inspection mainly focuses on functions, pages, interactions, etc.
-
Function: Completeness of each function
-
Page: Full display, no obstruction
-
Interaction: The interaction between pages and functions. From the user's perspective, is it acceptable and is there room for optimization?
4. Inspection plan
4.1. Clarify the scope of inspection
First, it is necessary to ensure the accuracy of the main process, then divide it according to business modules, sort out the inspection scope, and then refine the implementation effects of the functional modules that need attention based on the modules.
The following are the divided business modules and the scope that inspections need to cover:
After the modules are divided, specific module arrangements are carried out, and different arrangements are carried out for different inspection methods.
4.2. Organize business in advance
A business:
Although business A adopts a free inspection method, everyone is not completely familiar with each module, so the business process is sorted out in advance and shared before the inspection, so that they can be familiar with the business before the inspection and conduct a more in-depth inspection of the business process.
B business:
Organize the inspection cases of B business in advance, create test plans for different inspection cases for everyone before the inspection, provide reference during the inspection process, and verify each item.
4.3. Inspection frequency
Arrange a centralized inspection every week, lasting 1 to 2 hours, with QA, RD, and FE jointly participating.
4.4.QA responsibilities
Each inspection will arrange 2 on-duty QA, who are mainly responsible for answering cases and recording inspection problems. After the inspection, the submitted problems will be tracked, resolved and verified.
5.Problem record
Problem record: Record it in the form of bug and submit it to the corresponding development students.
Problem follow-up: Pay attention to the progress of problem solving and verify regressions.
Problem summary: Regularly summarize the types of problems, analyze the causes, and summarize experience, so that when implementing similar functions in the future, you will know what points need to be focused on and avoid repeating the same pitfalls multiple times.
Through the summary of problems, the problems mainly focus on coding errors, user experience, product design, and system compatibility, while the user experience problems mainly focus on small programs. Therefore, in the subsequent review stage, we will pay more attention to the rationality of product design, and in order to avoid daily work, we will strengthen the verification of the mini program to reduce the occurrence of experience problems.
6. Harvest
During the inspection, the biggest gain is the change of roles. First, as a QA student, you need to ensure the accuracy and completeness of each function. Secondly, we are also users, and we need to consider the rationality of the product from the user's perspective. We will continue to carry out business inspections in the future, not easily letting go of any online problems, and ensuring the final quality of our products.
Author: Hao Luyao
> Zhuanzhuan is a technical learning and exchange platform for R&D centers and industry partners, regularly sharing frontline practical experience and cutting-edge technical topics in the industry.
> Follow the public accounts "Zhuan Zhuan Technology" (comprehensive), "Da Zhuan Zhuan FE" (focused on FE), "Zhuan Zhuan QA" (focused on QA), and more useful practices, welcome to exchange and share~