Reading Notes 4-Test Case Design

Step 4: Test Case Design
No: Unique and helpful links to other documents such as test results and error reports;
Test Module: Large modules of this test case test;
Title: Description in one sentence
Purpose: Describes the purpose;
Test level: Level by importance;
Prerequisites: Preparations before executing this test case;
Input: Actions required for testing;
Expected output: Proper response, action, or display
Attention proposition
Appropriate coverage
Keep up with document changes
Repetition rate is limited to a moderate range
"To test and maintain"
Reuse between different products
Elements of Test Cases
Test Case coverage Requirements Matrix tracking function points with higher confidentiality within the scope permitted by the Budget

how to keep up with development document changes
how to limit the repetition rate of test cases to a moderate range repeated check cost input and output
methods to avoid duplication: 1. Optimize the database structure of the test case, and perform detailed classification, accurate keywords
2. Some redundancy should be tolerated for simple or important functions.
3. It takes a long time to execute complex test cases, and strict checks should be performed for repeated tests;
4. It does not make sense to test the number of test cases.
how to update" test cases by test and maintenance " free test and update test cases
How to reuse test cases among different products principle: avoid designing overly specific test cases, and minimize the coverage of a single test case.