Test Case Design

Design test cases based on requirement documents, and establish traceability between acceptance criteria and test cases.

Language Rules

Support questions in Chinese and English
Respond uniformly in Chinese
Generate documents in Chinese

Trigger Conditions

User has completed the requirement document
User requests test case design
User needs test coverage strategy

Preconditions

Requirement document:
```
docs/devdocs/01-requirements.md
```
System design document:
```
docs/devdocs/02-system-design.md
```
(Required to understand interface signatures and module division when designing UT/IT)
If not present, it is recommended to run the pre-phase first

Core Concepts

Test Case Sources

Feature Point (F-XXX)
    │
    └── User Story (US-XXX)
            │
            └── Acceptance Criterion (AC-XXX)
                    │
                    ├── Unit Test (UT-XXX)  ← Verify internal logic
                    │
                    ├── Integration Test (IT-XXX)  ← Verify component collaboration
                    │
                    └── E2E Test (E2E-XXX) ← Verify user scenarios

Key Principles:

Test cases are derived from requirements, not from code
Each acceptance criterion must be covered by at least one test case
Test type is selected based on the nature of the acceptance criterion

Test Type Selection

Acceptance Criterion Type	Recommended Test Type	Example
Input validation rules	Unit Test	"Email format validation" → UT
Business logic rules	Unit Test + Integration Test	"Password encrypted storage" → UT + IT
User interaction flow	E2E Test	"Complete registration process" → E2E
Inter-component collaboration	Integration Test	"Send verification email" → IT

Naming Convention

Test Type	Prefix	Format	Example
Unit Test	UT	UT-XXX	UT-001, UT-002
Integration Test	IT	IT-XXX	IT-001, IT-002
E2E Test	E2E	E2E-XXX	E2E-001, E2E-002

Workflow

1. Read requirement document
   │
   ▼
2. Extract feature points, user stories, and acceptance criteria
   │
   ▼
3. Select test type for each acceptance criterion
   │
   ▼
4. Design unit test cases (UT-XXX)
   │
   ▼
5. Design integration test cases (IT-XXX)
   │
   ▼
6. Design E2E test cases (E2E-XXX)
   │
   ▼
7. Generate traceability matrix
   │
   ▼
8. User confirmation

Output Files

Main File:

docs/devdocs/03-test-cases.md

Document Splitting Rules

Split the document when any of the following conditions are met:

Total number of test cases exceeds 30
Document exceeds 300 lines
Number of test cases for a single test type exceeds 15

Splitting Method:

docs/devdocs/
├── 03-test-cases.md           # Main document: Test strategy, coverage requirements, traceability matrix
├── 03-test-unit.md            # Unit test cases (UT-XXX)
├── 03-test-integration.md     # Integration test cases (IT-XXX)
└── 03-test-e2e.md             # E2E test cases (E2E-XXX)

Content Allocation After Splitting:

File	Content Included
03-test-cases.md	Test strategy, coverage requirements, traceability matrix, test case summary
03-test-unit.md	Details of all unit test cases (UT-001 ~ UT-XXX)
03-test-integration.md	Details of all integration test cases (IT-001 ~ IT-XXX)
03-test-e2e.md	Details of all E2E test cases (E2E-001 ~ E2E-XXX)

Content Retained in Main Document:

Test strategy description
Coverage targets
Complete traceability matrix (F → US → AC → Tests)
Description of test case scope for each sub-document

Small Projects: If the number of test cases is small (<30), they can be merged into a single file

03-test-cases.md

For detailed templates, refer to:

templates/test-cases-template.md
templates/unit-test-template.md
templates/integration-test-template.md
templates/e2e-test-template.md

Test Case Overview Document Structure

markdown

# Test Cases: <Feature Name>

## 1. Test Strategy
## 2. Coverage Requirements
## 3. Traceability Matrix
## 4. Test Case Summary

Traceability Matrix

The traceability matrix is the core deliverable, showing the complete association between requirements, tests, and code.

Basic Format (Design Phase)

markdown

| Feature Point | User Story | Acceptance Criterion | Unit Test | Integration Test | E2E Test | Status |
|---------------|------------|----------------------|-----------|------------------|----------|--------|
| F-001 | US-001 | AC-001 | UT-001 | - | E2E-001 | ⏳ |
| F-001 | US-001 | AC-002 | UT-002 | - | E2E-001 | ⏳ |
| F-001 | US-002 | AC-004 | UT-003, UT-004 | IT-001 | - | ⏳ |

Complete Format (Development Phase, Including Code Locations)

Code locations are automatically populated by
/devdocs-sync --trace
, based on scanning
@satisfies
/
@verifies
annotations in the code.

markdown

| AC ID | Acceptance Criterion | Test ID | Entry Code | Test Code | Status |
|-------|----------------------|---------|------------|-----------|--------|
| AC-001 | Email format validation | UT-001 | `src/user.ts:15` | `tests/user.test.ts:20` | ✅ |
| AC-002 | Password strength validation | UT-002 | `src/user.ts:15` | `tests/user.test.ts:35` | ✅ |
| AC-003 | Username uniqueness | UT-003 | `src/user.ts:15` | `tests/user.test.ts:50` | ⏳ |
| AC-004 | Send verification email | IT-001 | - | - | ❌ |

Code Location Field Description

Field	Source	Description
Entry Code	`@satisfies AC-XXX` annotation	Location of the method implementing this AC
Test Code	`@verifies AC-XXX` annotation	Location of the test verifying this AC

Status Description

Status	Meaning	Condition
✅	Fully Covered	Has test case + entry code + test code + test passed
⏳	In Progress	Has test case, code/test partially completed
⚠️	Partially Covered	Has code but lacks test, or has test but lacks code
❌	Not Covered	No test case or no code implementation

Matrix Maintenance Process

Design Phase                Development Phase          Sync Phase
    │                          │                           │
    ▼                          ▼                           ▼
Generate Basic Matrix    Generate skeleton code (with annotations)   /devdocs-sync --trace
(AC → Test IDs)          (Entry + Test)                      │
                                                        ▼
                                                 Scan code annotations
                                                        │
                                                        ▼
                                                 Populate code location column
                                                        │
                                                        ▼
                                                 Update status column

Test Case Format

Unit Test Case

markdown

| ID | Acceptance Criterion | Test Object | Scenario | Input | Expected Output | Priority |
|----|----------------------|-------------|----------|-------|-----------------|----------|
| UT-001 | AC-001 | validateEmail() | Valid email | "test@example.com" | true | P0 |
| UT-002 | AC-002 | validateEmail() | Invalid format | "invalid" | false | P0 |

Integration Test Case

markdown

| ID | Acceptance Criterion | Test Scenario | Involved Components | Expected Result | Priority |
|----|----------------------|---------------|---------------------|-----------------|----------|
| IT-001 | AC-004 | Password encrypted storage | UserService + DB | Password stored in bcrypt format | P0 |

E2E Test Case

markdown

| ID | User Story | Acceptance Criterion | Operation Steps | Expected Result | Priority |
|----|------------|----------------------|-----------------|-----------------|----------|
| E2E-001 | US-001 | AC-001~AC-003 | 1. Open registration page<br>2. Enter email and password<br>3. Click register | Registration successful, verification email received | P0 |

Coverage Requirements

Test Type	Coverage Target	Coverage Requirement
Unit Test	Core business logic	Line coverage ≥ 80%, branch coverage ≥ 80%
Integration Test	Component collaboration scenarios	At least 1 IT per feature point
E2E Test	User stories	At least 1 E2E per P0 user story

Constraints

Traceability Constraints

Each acceptance criterion must be covered by at least 1 test case
Must generate a traceability matrix
The traceability matrix must cover all ACs

Test Case Design Constraints

Test cases must be associated with acceptance criterion IDs
Each test case must have a clear expected result
Priority must be marked (P0/P1/P2)

Coverage Constraints

100% test coverage must be achieved for P0 acceptance criteria
P0 user stories must have E2E tests
Unit test line coverage target ≥ 80%

Quality Constraints (Refer to

/testing-guide

)

Test names must describe expected behavior
Weak assertions are prohibited (toBeDefined, toBeTruthy cannot be used as the only assertion)
Mocks are only used for external dependencies

Skill Collaboration

Scenario	Collaborating Skill	Description
Requirement Input	`/devdocs-requirements`	Pre-requisite: Provide F/US/AC as the basis for test design
New Feature Testing	`/devdocs-feature`	Called: New features require additional test cases
Bug Regression Testing	`/devdocs-bugfix`	Called: Bug fixes require supplementary regression tests
Test Improvement	`/devdocs-insights`	Called: Improvement suggestions may require test coverage
Traceability Update	`/devdocs-sync`	Collaboration: Trace mode updates code locations in the traceability matrix
Test Quality	`/testing-guide`	Collaboration: Quality constraints when writing test code
Task Splitting	`/devdocs-dev-tasks`	Follow-up: Convert test cases into development tasks

Next Steps

After completion, it is recommended to run

/devdocs-dev-tasks

for development task splitting.

devdocs-test-cases

NPX Install

Tags

SKILL.md Content (Chinese)

Test Case Design

Language Rules

Trigger Conditions

Preconditions

Core Concepts

Test Case Sources

Test Type Selection

Naming Convention

Workflow

Output Files

Document Splitting Rules

Test Case Overview Document Structure

Traceability Matrix

Basic Format (Design Phase)

Complete Format (Development Phase, Including Code Locations)

Code Location Field Description

Status Description

Matrix Maintenance Process

Test Case Format

Unit Test Case

Integration Test Case

E2E Test Case

Coverage Requirements

Constraints

Traceability Constraints

Test Case Design Constraints

Coverage Constraints

Quality Constraints (Refer to
`/testing-guide`
)

Skill Collaboration

Next Steps

devdocs-test-cases

NPX Install

Tags

SKILL.md Content (Chinese)

Test Case Design

Language Rules

Trigger Conditions

Preconditions

Core Concepts

Test Case Sources

Test Type Selection

Naming Convention

Workflow

Output Files

Document Splitting Rules

Test Case Overview Document Structure

Traceability Matrix

Basic Format (Design Phase)

Complete Format (Development Phase, Including Code Locations)

Code Location Field Description

Status Description

Matrix Maintenance Process

Test Case Format

Unit Test Case

Integration Test Case

E2E Test Case

Coverage Requirements

Constraints

Traceability Constraints

Test Case Design Constraints

Coverage Constraints

Quality Constraints (Refer to /testing-guide)

Skill Collaboration

Next Steps

Quality Constraints (Refer to
`/testing-guide`
)