How to avoid bugs and missed tests in mobile app testing

The following is an analysis of the measures taken when defects are missed:


in the requirements review stage, the details of business requirements are not clearly understood, and the implied expansion requirements are not deeply explored:

improvement measures Before

requirements review, we should carefully read the prd and interactive documents, and Form your own thinking about the product, list the question points about the product design through a mind map, and find out the product design

defect ; in

the requirement review meeting, bring the listed question points to the product, development Communicate your doubts and doubts about the product, and mention a few more whys? How to achieve? Source of data acquisition? How to deal with unexpected data? How is the cache handling mechanism? Where is the data stored? Is the logic handled by the frontend or served by the backend? Is the backend service logic associated with a third party?

After the requirements review is completed, according to certain functions, the requirements are divided into several large modules, the large modules are divided into small function points, and then the specific implementation process


of the function points is considered. Incomplete coverage of test cases and omissions in scenarios:

improvement measures

Use cases After the design is completed, organize the use case review

(1) Organize the development and product test case review, and throw out the questions during the use case design, and review and improve the use case from the perspective of product implementation, data storage, and product experience.

(2) If there is enough time, it is also very necessary to organize the use case review in the test group, especially some experienced or familiar business drivers, who can quickly help point out the omissions of the use case in the use case review, which is helpful for the testers. Open up your ideas and cover as many user scenarios as possible. It is worth noting that if you encounter uncertainties in the use case review, you should record them immediately, and find relevant personnel to confirm in time after the end to avoid guesswork.

Improve use cases based on online user feedback defects

After the product test is released online, for the defects reported by users, if the defects are caused by incomplete scene design, we will first analyze whether the scene with the problem must occur or occasionally. Confirm some specific reproduction steps of the scenario, and confirm the introduction reasons and solutions. Then complete the test case: In addition to supplementing the scenario case, consider some scenarios related to the scenario, improve and review the test cases in a variety of scenarios in a timely manner, and add them to the use case library.


Failure to strictly follow test cases in the testing phase:

Improvement measures

Test cases may not guarantee that all scenarios and function points can be covered, but strictly following test cases can ensure product quality to the greatest extent and avoid defects as much as possible.

In addition, develop the habit of test recording: For test blocking use cases and test fail use cases, you should focus on and record them, and perform accurate regression tests in the regression test phase to ensure that new bugs introduced by related functions due to bug fixes can also be discovered.

The testing environment and testing resources are limited, resulting in missed testing of defects:

Improvement measures

Introducing grayscale release testing

The testing team conducts regression testing on the pre-release environment, which can basically simulate the real environment to execute use cases that cannot be tested in the testing environment without affecting online normal use of the user.

New bugs introduced by developers:

improvement measures

Code review

is from the code management level: develop and fix a bug and submit the code for self-test. When the development team submits the code for code review, it is less likely to introduce new bugs.

Accurate regression testing

From the level of self-cultivation in testing: after developing and testing, through diff codes, we can understand the code change points, accurately analyze the impact of the change points on the associated function points, confirm and verify the bugs fixed by developers, and The associated function points are tested in the app as much as possible Stages are tested by traversal regression.