How to conduct test case review

Test case review is an important part of testing activities , Review test cases , It can effectively find the deficiencies in use cases , And better complement , To avoid missing test scenarios or inconsistent understanding of business logic . that , How to do a good job of test case review ？

01

Do a good job in grading test cases , Not all test cases need to be reviewed , Or some use cases need to be digested internally . In general , I will divide test cases into three levels ：

Page function use case :

The main verification is the page function , For example, common data increase 、 Delete 、 Change 、 check , Page shows 、 Key function 、 Layout and simple data flow verification . Such use cases are not recommended for use case review , If there are more new people in the Group , Such use cases should be checked by the person in charge of the test .

Business process use cases ：

Based on user behavior , Verify the correlation of various sub modules within the system through scenario cases , Ensure the orderly flow of data and status 、 normal , Abnormal data can be handled normally or given clear prompts . Such use cases are the focus of the review , It is also the core content of requirements , We need to focus on the review .

Cross system interface use cases ：

As the complexity of the business increases , We may need to deal with other systems more , In cross system interface function verification , We need to be clear about what the expected checkpoints are ; The exception use cases that need to be considered fall into two categories ,1 Class is how to accept upstream exceptions （ Whether the status is returned 、 Whether the modification of upstream data will affect the system ）2 It is the influence of the abnormality of our own system on the upstream and downstream systems .

02

How to better carry out test case review ？ The author's experience is as follows ：

focusing ： Each use case review shall not exceed 1 Hours , Only review the core content and test design ideas , Do not review each specific use case , In fact, it doesn't make much sense , As long as the test idea is ok , Generally, there will be no deviation ;

Prepare in advance ： Communicate with R & D and products in advance , Let them read the document in advance . During the review , There is no need to pull everyone , Only relevant personnel are needed

Continuous feedback ： Test cases are not static , Even after the review . Don't let test cases become an excuse （ Many testers often tell others that they will not raise it during the review , This practice is not recommended , Others just help you check, Instead of letting him think for you ）

Give action items ： What needs to be revised , Timely revise and feed back , Let everyone have a sense of participation , And thank you .

Pay attention to the granularity of the test case , At the time of review , There is no need to go through one by one , Review the test ideas . In essence, test cases are also a process of visualizing test thinking , Unless your testing team is particularly young （ For example, the first kind of test cases , Not suitable for large-scale Review ）

03

Don't use case reviews as a burden , Preparation before doing good , Take advantage of this opportunity , Another opportunity to align requirements understanding . It can ensure that everyone has the same understanding of the same demand , Avoid more possible rework waste .

Friends who like software testing , If my blog helps you 、 If you like my blog content , please “ give the thumbs-up ” “ Comment on ” “ Collection ” One Key triple connection ！