Test Case Review (Chinese Version)

test-case-reviewer-en

prompts/test-case-reviewer.md

When to Use

• User mentions "test case review", "test case review", or "test case assessment"
• Need to conduct quality review, missing scenario mining, and improvement suggestions for existing test cases
• Trigger Examples: "Please review the following test cases" "Identify omissions and risks in the test cases"

Output Format Options

How to Use

1. Open the corresponding prompt file under

   prompts/

   in this directory and copy the content below the dashed line.
2. Attach your requirements and context (business processes, environment, constraints, acceptance criteria).
3. If non-Markdown output is needed, append the request sentence from

   output-formats.md

   at the end.

Reference Files

• prompts/test-case-reviewer.md — Test Case Review Prompt
• output-formats.md — Format Specifications

代码示例 | Code Examples

1. Test Case Review Standards (In Plan) - Review checklist and standards

常见误区 | Common Pitfalls

• ❌ Only look at surface issues → ✅ Deeply analyze coverage and quality
• ❌ Criticize without suggestions → ✅ Provide specific improvement recommendations
• ❌ Ignore maintainability → ✅ Evaluate long-term maintenance costs
• ❌ Lack priority marking → ✅ Mark issue severity levels

最佳实践 | Best Practices

1. Review Dimensions

• Requirement coverage
• Scenario coverage
• Boundary value coverage
• Exception scenario coverage

• Clear steps
• Specific data
• Verifiable results
• No ambiguity

• Independent test cases
• Data separation
• Modular design
• Easy to update

• Reasonable execution time
• No redundant steps
• Automation potential
• ROI evaluation

2. Review Checklist

## Test Case Review Checklist

### Basic Information
- [ ] Unique test case ID
- [ ] Clear title
- [ ] Priority marked
- [ ] Type marked

### Preconditions
- [ ] Complete preconditions
- [ ] Feasible preconditions
- [ ] Clear dependency relationships

### Test Steps
- [ ] Detailed and specific steps
- [ ] Repeatable steps
- [ ] Clear step numbering
- [ ] No missing steps

### Test Data
- [ ] Specific and clear data
- [ ] Accessible data
- [ ] Covers boundary values
- [ ] Includes abnormal data

### Expected Results
- [ ] Clear results
- [ ] Verifiable results
- [ ] Complete results
- [ ] No ambiguous descriptions

### Coverage
- [ ] Normal scenarios
- [ ] Exception scenarios
- [ ] Boundary conditions
- [ ] Permission verification

3. Test Case Review Report Template

## Test Case Review Report

**Review Date**: 2024-02-06
**Reviewer**: Zhang San
**Number of Test Cases**: 50
**Review Scope**: Login Module

### Review Summary
- Overall Quality: Good
- Key Issue: Insufficient boundary value coverage
- Improvement Suggestion: Add exception scenarios

### Issue Statistics
| Severity | Count | Percentage |
|---------|------|------|
| Critical | 2 | 4% |
| High | 5 | 10% |
| Medium | 10 | 20% |
| Low | 8 | 16% |

### Detailed Issues

#### Critical Issues
1. **TC-001**: Missing SQL injection test
   - **Impact**: Security risk
   - **Suggestion**: Add special character tests

#### High Issues
2. **TC-005**: Incomplete boundary value testing
   - **Impact**: Potential defect omission
   - **Suggestion**: Supplement boundary value test cases

### Missing Scenarios
- Concurrent login test
- Session timeout test
- Password complexity verification

### Improvement Suggestions
1. Add boundary value testing
2. Supplement exception scenarios
3. Optimize test case descriptions
4. Add automation tags

故障排除 | Troubleshooting

Issue 1: Don't know how to review

Issue 2: Low review efficiency

1. Use review tools
2. Batch review similar test cases
3. Focus on reviewing high-priority test cases

Target Audience

• QA and developers working in this testing domain on real projects
• Test leads who need structured, reusable test deliverables
• AI users who need to quickly generate actionable test outputs

Non-Applicable Scenarios

• Pure online emergency handling without test scope context
• Decisions requiring final legal/compliance ruling without expert review
• Requests lacking minimum inputs (scope, environment, expected behavior)

Key Success Factors

• Clarify scope, environment, and acceptance criteria before generating test content
• Generated results must be re-validated against real system constraints
• Maintain traceability of deliverables (Requirements -> Test Points -> Defects -> Decisions)

Output Templates and Parsing Scripts

• Template Directory:

  output-templates/

  • template-word.md

    (Word-friendly structure)

  • template-excel.tsv

    (Excel paste-ready)

  • template-xmind.md

    (XMind structured outline)

  • template-json.json

  • template-csv.csv

  • template-markdown.md

• Parsing Script Directory:

  scripts/

  • General Parsing:

    parse_output_formats.py

  • Format-specific Parsing:

    parse_word.py

    ,

    parse_excel.py

    ,

    parse_xmind.py

    ,

    parse_json.py

    ,

    parse_csv.py

    ,

    parse_markdown.py

  • General Conversion:

    convert_output_formats.py

  • Format-specific Conversion:

    convert_to_word.py

    ,

    convert_to_excel.py

    ,

    convert_to_xmind.py

    ,

    convert_to_json.py

    ,

    convert_to_csv.py

    ,

    convert_to_markdown.py

  • Batch Conversion:

    batch_convert_templates.py

    (outputs to

    artifacts/

    in batches)

python3 scripts/parse_json.py output-templates/template-json.json
python3 scripts/parse_markdown.py output-templates/template-markdown.md
python3 scripts/convert_to_json.py output-templates/template-markdown.md
python3 scripts/convert_output_formats.py output-templates/template-json.json --to csv
python3 scripts/batch_convert_templates.py --skip-same