1. Purpose
Providing a reference standard for the evaluation use cases, to ensure coverage and effectiveness reviews
2. area
This document is intended audience for all members of the project managers, test engineers and project groups, suitable for any products and projects.
3, classification review
- Internal review of the test group: Test department members to participate
- Internal review of the project team: project managers, product, developers and testers to participate
4, content review
- Structural arrangements for the use case designs are clear, reasonable, beneficial and efficient coverage of needs.
- Priority arrangement is reasonable.
- Whether to cover all testing requirements on function points
- Example whether good use enforceable. Example precondition for example, the step, the input data and expected results are clear and correct; whether expected results significantly authentication method
- You have to delete redundant use cases
- Contain sufficient negative test cases. Full definition, if the rule here 8 & 2, that is 4 times the amount used in Example front, after a robust software, the code is 80% in the "Protection" function to achieve 20%
- Whether from the user level to design user scenarios and test cases using the process
- Whether simple, strong reusability. For example, the high repeat steps or processes is defined as the number of extracted reusable standard procedures.
5, review the way
- Held a review meeting. The participants give comments and suggestions after the designer explained, while detailed review of records
- General OA communicate with stakeholders
6, the end of the assessment criteria
Feedback collected relevant personnel 1) review process (ie problem record list), and update the test case on this basis until the review through;
Attachment: test case review checklist items:
1) whether the test cases prepared in accordance with company-defined templates;
2) Description of the test itself is clear, whether there is ambiguity;
3) Test Case content is correct and consistent with the needs of the target;
4) test to determine whether a desired result, only;
5) whether the procedure should be consistent with the description;
6) whether the test case to cover all needs;
Whether 7) designed to test the presence of redundancy;
8) test whether the enforceable;
9) whether the user level test cases to design user scenarios and business processes;
10) whether the test case covering the scene of the most complex business processes;
11) designed to contain positive cases and negative cases of use;
12) the output item is automatically generated by the system indicate whether the generation rule;
13) test should include intermediate inspection and background data;
14) test cases should be the correct name and number;
15) should be labeled with the test case execution priority;
16) configuration information related to the test case comprising: a test environment, data, pre-test, the user permissions;
17) for each test case steps should be <= 15 Step.