Skip to content

Commit 05e52dc

Browse files
shinprclaude
andcommitted
feat: add Acceptance Criteria and enhanced Testing Strategy to English design template
Aligned template-en.md with template-ja.md by adding: - Acceptance Criteria section for verifiable implementation conditions - Enhanced Testing Strategy with test design principles - E2E testing approach for complete scenario verification - Clear linkage between acceptance criteria and test cases These additions improve AI execution accuracy by providing clear, measurable success criteria. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
1 parent b212003 commit 05e52dc

File tree

1 file changed

+27
-0
lines changed

1 file changed

+27
-0
lines changed

docs/design/template-en.md

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,18 @@
2727
- **Reliability**: [Requirements for error rate, availability, etc.]
2828
- **Maintainability**: [Code understandability, ease of modification]
2929

30+
## Acceptance Criteria
31+
32+
Define specific and verifiable conditions to determine successful implementation for each functional requirement.
33+
These conditions serve as the basis for test cases and are used to objectively determine implementation completion.
34+
35+
- [ ] [Specific acceptance criteria for functional requirement 1]
36+
- Example: "When a user clicks the login button, authentication succeeds with valid credentials"
37+
- Example: "When invalid credentials are provided, an appropriate error message is displayed"
38+
- [ ] [Specific acceptance criteria for functional requirement 2]
39+
- Example: "The data list screen displays items paginated by 10 entries"
40+
- Example: "When text is entered in the search field, results are filtered in real-time"
41+
3042
## Design
3143

3244
### Architecture Overview
@@ -81,17 +93,32 @@
8193

8294
## Testing Strategy
8395

96+
### Test Design Principles
97+
98+
Automatically derive test cases from acceptance criteria:
99+
- Create at least one test case for each acceptance criterion
100+
- Implement measurable criteria from acceptance criteria as assertions
101+
84102
### Unit Tests
85103

86104
[Unit testing approach and coverage goals]
105+
- Verify individual elements of functional acceptance criteria
87106

88107
### Integration Tests
89108

90109
[Integration testing approach and important test cases]
110+
- Verify combined behavior of functional acceptance criteria
111+
112+
### End-to-End Tests
113+
114+
[E2E testing approach]
115+
- Verify complete scenarios from acceptance criteria
116+
- Confirm functional behavior from user perspective
91117

92118
### Performance Tests
93119

94120
[Performance testing methods and criteria]
121+
- Verify performance benchmarks from non-functional acceptance criteria
95122

96123
## Security Considerations
97124

0 commit comments

Comments
 (0)