background
A comprehensive summary of the product has recently been made. Product, development, and testing are conducted together to conduct a comprehensive review and analysis of past requirements. The product summarizes detailed product requirements description documents. In order to ensure the quality of the software, a comprehensive review of the product use cases is also carried out to improve the coverage of test cases.
The following are some tips on improving the coverage of test cases at work.
Measure 1: Improve the breadth and depth of product business knowledge
Based on work experience, test cases designed solely relying on requirements documents can basically achieve basic functional coverage of use cases. Then based on the product's problems exposed in the simulation disk operation, the product added the points of attention to the requirements document, developed and fixed the bug, tested the additional use cases and tested it, it seems that the function has been fully covered.
However, it is impossible for the requirements document to cover all the situations that need to be considered, and more only describe the most basic function points. Designing test cases is limited by relying solely on requirements documents. I think solving this problem requires the subjective initiative of the use case designer, the grasp of the software testing theory, the theoretical knowledge does not have much room for expansion, and the breadth and depth of business knowledge (Measure 2) Very good to do this)
Measure 2: Summarize
Memory and experience are very limited. It is difficult to fully consider all the instantaneous situations. Let's hand it over to generalization.
Summarize with a single action, for example: selling a stock, this is an action. The situation of this action is summarized according to the previous selling situation (see the figure below). When the design of the use case design to the action of selling stocks in the future, you only need to check this summary chart to fully understand the various possibilities. In this way Design use cases can well improve the design use cases while avoiding omissions in a certain situation. When the subsequent work encounters a new selling point or when the demand changes at a certain point, the summary diagram is timely Just update it.
Measure 3: Expand the coverage of unit testing and integration testing
Relying on the summary diagram and requirements document of the second measure, in the unit test of a single function of the use case design, it is easy to achieve comprehensive coverage of the use case. The more comprehensive the use case coverage of each function point is, the more situations are considered in the integration test, and the more comprehensive the use case coverage is.