What is the use case review?
The main use case is to review the work product, developers and testers can be used for test cases and test project to do.
· The purpose of the use case review
In order to reduce the execution phase testers do inefficiencies; (execution invalid case, filed invalidity)
in order to avoid inconsistencies tripartite needs to understand;
to quality standards and requirements of the project for each tester standard agreement.
Test case review process specification added to the test and try out more than two months, during the feedback of the parties who, in order to improve efficiency and use cases reviewed, specially formulated according to the following use case specification review:
First, the preparatory work before review what needs to be done
1, the end of the needs assessment, we can begin to split the demand function point.
Tool: use XMind, must include the expected results and the test results, Android and iOS test results can be used to distinguish between labels marked. Advantages: Videos mind mapping manner, the logic is clear, easy to reviewers (and product developers) Quick View, high efficiency assessment.
It should be noted that many testers prefer to use Excel design use cases, I am no exception, but according to the test after a period of product development and communication, we all feel that writing mind map with XMind way better, look more convenient. So what tools specific method used, it may be adjusted according to personal hobby, but the goal is the same, so that effective and efficient use cases to carry out the assessment and generate value.
2, the feature point and then broken down into specific test.
Here required completion expected results and the actual test results on a mind map, facilitate the follow-up test results.
3. After writing use cases, make their first self-test , self-test, for the point in question have set out in advance with product development, will decide after the results of perfect use case, there is still doubt can flag it will be assessed on the throw to discuss.
4, and reviewers (and product development) determine a good time to review and advance specific test cases sent to the participants view.
Second, use case review participants
The main product is developed (client and back-end), test, project manager, operations.
Note: The above personnel must be participants, and other project quality, schedule the officer, according to the actual situation may be invited to participate.
Third, the review time by Example
For agile development project, it recommended control in less than half an hour.
If you think that complex needs, function much point, a half-hour speech about them, then I suggest you prioritize feature points higher priority review priority use cases, then doubt many use cases reviewed for the last to feature the simple use cases may simple passing. Always remember that the goal of our review of the use cases, can not be a mere formality.
Fourth, the form of evaluation used in Example
1, a control test, from top to bottom, left to right, one by one to read.
This is the practice of many companies, if you did the same thing, I believe you do not necessarily like it, because it is time-consuming, misplaced priorities, passion and attention of participants gradually reduced, low efficiency of the entire use case review as host also talked about thirsty, less effective.
2, the first complex function, high priority, review questions and more use case, then a simple evaluation function, the function of lower priority points.
For the review process, half of the problem will no conclusion can be recorded, as the focus of discussion will follow up.
This approach has many advantages, beginning a period of review, we focus on, to participate in high passion, this time to discuss difficult issues in question, and high efficiency. The most important thing to do first.
In addition, the entire review will prioritize, slow climax there are points to be more efficient to achieve the purpose of our review.
V. formal review
A formal review process need to pay attention to a few details, if you have done it, it can be said that the entire review was successful and valuable.
1, the complexity of use cases Yaoan priority function for review;
2, the assessment process as far as possible, clear thinking, describes each feature point with the most concise language;
3, more than five minutes can not determine the outcome of the discussion will be reserved for later follow-up.
Sixth, after the end of the assessment needs to do something?
Not to say that the assessment will end, and gets the job done, in fact, for the entire review use cases, this half-done.
After the review, the first time to sort of test cases, the modified content refresh completion.
At the meeting undetermined content, after we will continue to follow up until the result of the determination.
Nowhere in question, and then make a simple use case review meeting summary (as amended which features point, complement what? What module features are subject to change? What features do postponed to next? Etc.), this summary give yourself the entire use-case assessment summary, at the same time to be synchronized to the other members of the project team, good information sharing, it is very important.
Well, the whole complete review of the use cases and needs attention is about all, want to test group of people seriously look at, and the implementation of specific work. According to the actual situation of individual local projects can flexibly change, finally, there is a problem please feel free to communicate.
Author: Wood 0524
link: https: //www.jianshu.com/p/3a89f0ffc1ab
Source: Jane book
Jane book copyright reserved by the authors, are reproduced in any form, please contact the author to obtain authorization and indicate the source.