Shulou(Shulou.com)06/03 Report--

You Test Cloud Service platform is a mobile cloud testing platform, with more than 50 testing experts, more than 300 professional testing teams, and more than 10 years of terminal testing service experience, providing compatibility testing, automated testing, cloud machines, device sharing and other services.

I have a deep feeling about the recent use case review. Here are some of my feelings about test case review, which are sent for everyone to discuss and learn.

Listen to your complaints about test case review?

"Test case design is a matter of testing, so why do the reviews want us to participate?"

"there are already a lot of test cases. I don't know what to review. What can I provide?"

"use case review is too boring. Does the 200th use case case comment one by one?"

"this is a function developed by others, and it has nothing to do with me."

I believe that the above sentences are often heard by reviews, so why review test cases?

Here, we analyze the purpose and significance of the use case review from several roles (test, development, product manager, project manager).

Test:

As different test students have different understanding of requirements and use case design, in order to improve the integrity, rationality and efficiency of use cases, we can use the way of review to converge the opinions of different people and different professionals to enrich test cases. Testing is endless, and no one can guarantee the complete coverage of their design use cases.

Development:

Testing and development do not agree on requirements understanding, and double check requirements through review and development to ensure consistency of requirements understanding before testing, so as to avoid disputes and wrangling in the process of testing.

Leak out the development in the implementation process where the code logic is not fully considered, early warning, to avoid the defects caused by inadequate logic processing.

Developers can review the use cases from the implementation level and supplement the test cases because the testers do not understand the lack of test cases caused by the implementation process.

Product Manager:

Often in the test case design stage, some details can not be known from the requirements document, need to communicate frequently with the product manager; some do not communicate to the existence of inconsistent understanding or inadequate consideration. The product manager participates in the use case review, and they can help you identify more problems, and during the review process, you can also help the product manager identify some areas that he has not considered fully in the product design process. Good test cases are more specific than requirements documents.

Project Manager:

Through the use case review, we can not only evaluate whether the test case is sufficient to cover all the requirement logic, but also evaluate the test workload by means of review. If 100 use cases can be carried out by two people a day, the test time can be scheduled according to the number of test cases. Of course, the execution time may be different for different use cases, but the number of use cases does measure the cost of labor consumption to some extent.

Therefore, in this review process, the project manager needs to review the coverage and redundancy of test cases.

1. The timing of the review

First of all, we have to say that the time of use case design must be carried out after the requirements review. No matter how thoughtful the use case design is, some of the ideas at that time will be forgotten in a day or two. So first do a good job of sorting and recording. After participating in the technical review of the development, revise and supplement it according to the way the developer realizes the requirements.

The best time for use case review is in the mid-development phase:

If the use case review is initiated in the early stage of development, the technical review of the development may not have begun, and the test does not have enough time to sort out the ideas of test design, resulting in low quality of use cases. If the use case review is initiated at the completion of the development phase, the leakage in the use case review process is likely to be caused by inadequate consideration or inconsistent understanding between the product manager and the development. the problem is exposed later, which will lead to rework or version delay.

2. The process of review

The tester determines the review date and participates in the review

Two days before the review, the test cases are sent to all reviewers

Reviewers record test case issues

Review meeting, test case writers explain the use cases, participants put forward the review

End of meeting, modify use case, and email output

3. The content of the review

1. Whether the description is clear and ambiguous.

2. There is no dispute over whether the content is complete and whether it clearly includes input conditions and expected output results.

3. Whether it covers all scenarios, logical branches, constraints, etc.

4. whether which requirements are unpredictable: unable to prepare the environment, lack of testability, and so on.

5. Whether the execution efficiency of test cases is taken into account (redundant use cases)

4. Last few words

In the process of use case review, there is often a phenomenon that the participation of the reviewers involved in the use case review is not high, and the effect of the use case review is poor.

Usually, in the use case review, testers do not first explain the design ideas of their own use cases, but directly talk about the specific implementation cases. Usually an input condition, different scenarios, different operating steps, may generate a lot of use case case; if a review is really boring; and many use case case are normal logic, review is not meaningful.

When the test asks, "is there anything else you need to add?" It is estimated that the developer is also dizzy. If testers can adjust and explain the design ideas first during the review, they can help clarify the ideas of use case design and clarify the main points of testing through auxiliary means such as flow diagrams, use case diagrams, sequence diagrams, state diagrams, and so on. development is also easy to participate in the review process to enhance interaction Then in the review of use case case, and mainly exception case, normal logic of the use case case as far as possible to improve the efficiency of use case review, I believe that the participation of reviewers will be increased.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.