Test Case Review

Reprint Test Case Review

The first thing to know is the definition of internal review, the internal review of the Test team, or the review within the project team. The review is defined differently and the content is not the same.

I. Review classification: Test group Internal review

The review within the test group should focus on:

1. The description of the test case itself is clear, whether there is ambiguity;
2. Considering the execution efficiency of test cases, the steps of test cases are repeated repeatedly, the verification points are different, and the redundancy of test design results in inefficient.
3. Whether to target the demand tracking matrix, covering all the software requirements;
4. The requirements of the software are fully complied with. This is not certain, because even if the strict evaluation, there will be errors, the specific situation should be treated.

Project Team Internal review

If it is a review within the project team, it will require the review committee to do, the angle is different, the criteria for the review are different. Like what:

1. The person who collects the customer needs to pay attention to whether your business logic is correct;
2. The person who analyzes the software requirements specification pays attention to whether your use case is consistent with the specification requirements;
3. The development manager will focus on whether the requirements of your use case are reasonable.

Two. Test Case review Steps

The review of test cases can make the structure of use cases more clear, the coverage of user scenarios more comprehensive, and for test engineers is a rapid improvement of use case design ability process.

1. Reasons for the need for review

A test case is a guideline for software testing, but it is not a guideline once it is completed. As the design experience of use case developers and the depth of understanding of requirements are different, so the quality of use cases will inevitably have varying degrees of difference.

2. Timing of the review

First, it is to be reviewed after the initial design of the use case is completed;
The second is two reviews after the entire detailed use case is complete. If the project time is more tense, as far as possible to ensure the use case design review, early detection of the shortcomings.

3. Participation in the accreditation staff

• Department review, test department all members participate in the review.
• Company review, which includes project managers, demand analysts, architects, developers, and testers.
• Customer reviews, including developers and testers of the client side. This situation is more common in outsourced companies.

4. Judging the class capacity

1. Whether the structure arrangement of use case design is clear and reasonable, and whether it is advantageous to effectively cover the requirement.
2. Whether the priority arrangement is reasonable.
3. Whether to overwrite all feature points on the test requirements.
4. Whether the use case has a good enforceability. For example, the precondition of the use case, the execution steps, the input data and the expected result is clear and correct, and whether the expected result has obvious verification method.
5. Whether the redundant use cases have been removed.
6. Whether to include sufficient negative test cases. Fully defined, if the 2&8 rule is used here, it is 4 times times the number of positive use cases, after all a robust software, where 80% of the code is implemented in the "Protection" 20% function.
7. Whether to design test cases for user usage scenarios and use processes from the user level.
8. is concise, reusability is strong. For example, a high-repetition step or process can be extracted to define some reusable standard steps.

Personally, a "healthy" test case must pass at least the first 5 criteria.

5, the way of judging

1. Convene a review meeting. The attendees give comments and suggestions after the designers have explained them, and conduct detailed review records.
2. General email communication with related people
3. The general IM tool communicates directly with the relevant personnel only as a means of obtaining feedback from other people about the use case. In that way, the relevant documents of the use case design should be sent to the other party prior to the communication to save the communication cost.

6, the evaluation of the end of the standard

The feedback from the use case is collected in the review activity, and the use case is updated on this basis until the review is passed.

Test Case Review