musubi-sdd 3.0.0 → 3.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/bin/musubi-browser.js +0 -0
- package/bin/musubi-convert.js +0 -0
- package/bin/musubi-gui.js +0 -0
- package/bin/musubi-validate.js +0 -10
- package/package.json +1 -1
- package/src/templates/agents/claude-code/skills/ai-ml-engineer/mlops-guide.md +350 -0
- package/src/templates/agents/claude-code/skills/ai-ml-engineer/model-card-template.md +246 -0
- package/src/templates/agents/claude-code/skills/api-designer/api-patterns.md +336 -0
- package/src/templates/agents/claude-code/skills/api-designer/openapi-template.md +376 -0
- package/src/templates/agents/claude-code/skills/bug-hunter/root-cause-analysis.md +177 -0
- package/src/templates/agents/claude-code/skills/change-impact-analyzer/dependency-graph-patterns.md +348 -0
- package/src/templates/agents/claude-code/skills/change-impact-analyzer/impact-analysis-template.md +246 -0
- package/src/templates/agents/claude-code/skills/cloud-architect/aws-patterns.md +239 -0
- package/src/templates/agents/claude-code/skills/cloud-architect/azure-patterns.md +300 -0
- package/src/templates/agents/claude-code/skills/cloud-architect/terraform-templates/azure-webapp.tf +337 -0
- package/src/templates/agents/claude-code/skills/code-reviewer/best-practices.md +155 -0
- package/src/templates/agents/claude-code/skills/code-reviewer/review-checklist.md +184 -0
- package/src/templates/agents/claude-code/skills/code-reviewer/review-standards.md +272 -0
- package/src/templates/agents/claude-code/skills/constitution-enforcer/constitutional-articles.md +449 -0
- package/src/templates/agents/claude-code/skills/constitution-enforcer/phase-minus-one-gates.md +375 -0
- package/src/templates/agents/claude-code/skills/database-administrator/backup-recovery.md +331 -0
- package/src/templates/agents/claude-code/skills/database-administrator/tuning-guide.md +314 -0
- package/src/templates/agents/claude-code/skills/database-schema-designer/schema-patterns.md +335 -0
- package/src/templates/agents/claude-code/skills/devops-engineer/ci-cd-templates.md +443 -0
- package/src/templates/agents/claude-code/skills/devops-engineer/pipeline-templates/github-actions.yml +311 -0
- package/src/templates/agents/claude-code/skills/devops-engineer/pipeline-templates/gitlab-ci.yml +255 -0
- package/src/templates/agents/claude-code/skills/orchestrator/patterns.md +266 -0
- package/src/templates/agents/claude-code/skills/orchestrator/selection-matrix.md +185 -0
- package/src/templates/agents/claude-code/skills/performance-engineer/optimization-playbook.md +306 -0
- package/src/templates/agents/claude-code/skills/performance-optimizer/benchmark-template.md +272 -0
- package/src/templates/agents/claude-code/skills/performance-optimizer/optimization-patterns.md +273 -0
- package/src/templates/agents/claude-code/skills/project-manager/agile-ceremonies.md +283 -0
- package/src/templates/agents/claude-code/skills/project-manager/project-templates.md +345 -0
- package/src/templates/agents/claude-code/skills/quality-assurance/qa-plan-template.md +219 -0
- package/src/templates/agents/claude-code/skills/release-coordinator/feature-flag-guide.md +312 -0
- package/src/templates/agents/claude-code/skills/release-coordinator/release-plan-template.md +230 -0
- package/src/templates/agents/claude-code/skills/requirements-analyst/ears-format.md +259 -0
- package/src/templates/agents/claude-code/skills/requirements-analyst/validation-rules.md +359 -0
- package/src/templates/agents/claude-code/skills/security-auditor/audit-checklists.md +243 -0
- package/src/templates/agents/claude-code/skills/security-auditor/owasp-top-10.md +349 -0
- package/src/templates/agents/claude-code/skills/security-auditor/vulnerability-patterns.md +295 -0
- package/src/templates/agents/claude-code/skills/site-reliability-engineer/incident-response-template.md +286 -0
- package/src/templates/agents/claude-code/skills/site-reliability-engineer/observability-patterns.md +359 -0
- package/src/templates/agents/claude-code/skills/site-reliability-engineer/slo-sli-guide.md +302 -0
- package/src/templates/agents/claude-code/skills/software-developer/solid-principles.md +348 -0
- package/src/templates/agents/claude-code/skills/software-developer/test-first-workflow.md +370 -0
- package/src/templates/agents/claude-code/skills/steering/auto-update-rules.md +328 -0
- package/src/templates/agents/claude-code/skills/system-architect/adr-template.md +295 -0
- package/src/templates/agents/claude-code/skills/system-architect/c4-model-guide.md +328 -0
- package/src/templates/agents/claude-code/skills/technical-writer/doc-templates/documentation-templates.md +436 -0
- package/src/templates/agents/claude-code/skills/test-engineer/ears-test-mapping.md +444 -0
- package/src/templates/agents/claude-code/skills/test-engineer/test-types.md +425 -0
- package/src/templates/agents/claude-code/skills/traceability-auditor/coverage-matrix-template.md +131 -0
- package/src/templates/agents/claude-code/skills/traceability-auditor/gap-detection-rules.md +227 -0
- package/src/templates/agents/claude-code/skills/ui-ux-designer/accessibility-guidelines.md +318 -0
- package/src/templates/agents/claude-code/skills/ui-ux-designer/design-system-components.md +345 -0
- package/src/validators/constitutional-validator.js +494 -0
|
@@ -0,0 +1,345 @@
|
|
|
1
|
+
# Project Management Templates
|
|
2
|
+
|
|
3
|
+
## Overview
|
|
4
|
+
|
|
5
|
+
Templates for project planning, tracking, and reporting.
|
|
6
|
+
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
## Project Charter Template
|
|
10
|
+
|
|
11
|
+
```markdown
|
|
12
|
+
# Project Charter: [Project Name]
|
|
13
|
+
|
|
14
|
+
## Overview
|
|
15
|
+
| Field | Value |
|
|
16
|
+
|-------|-------|
|
|
17
|
+
| Project Name | [Name] |
|
|
18
|
+
| Project Manager | [Name] |
|
|
19
|
+
| Sponsor | [Name] |
|
|
20
|
+
| Start Date | YYYY-MM-DD |
|
|
21
|
+
| Target End Date | YYYY-MM-DD |
|
|
22
|
+
| Status | Planning / Active / Complete |
|
|
23
|
+
|
|
24
|
+
---
|
|
25
|
+
|
|
26
|
+
## 1. Project Purpose
|
|
27
|
+
[Why are we doing this project?]
|
|
28
|
+
|
|
29
|
+
## 2. Objectives
|
|
30
|
+
- [Objective 1]
|
|
31
|
+
- [Objective 2]
|
|
32
|
+
- [Objective 3]
|
|
33
|
+
|
|
34
|
+
## 3. Scope
|
|
35
|
+
|
|
36
|
+
### In Scope
|
|
37
|
+
- [Item 1]
|
|
38
|
+
- [Item 2]
|
|
39
|
+
|
|
40
|
+
### Out of Scope
|
|
41
|
+
- [Item 1]
|
|
42
|
+
- [Item 2]
|
|
43
|
+
|
|
44
|
+
## 4. Deliverables
|
|
45
|
+
| Deliverable | Description | Due Date |
|
|
46
|
+
|-------------|-------------|----------|
|
|
47
|
+
| [D1] | [Description] | [Date] |
|
|
48
|
+
| [D2] | [Description] | [Date] |
|
|
49
|
+
|
|
50
|
+
## 5. Success Criteria
|
|
51
|
+
- [Criterion 1]
|
|
52
|
+
- [Criterion 2]
|
|
53
|
+
|
|
54
|
+
## 6. Stakeholders
|
|
55
|
+
| Name | Role | Involvement |
|
|
56
|
+
|------|------|-------------|
|
|
57
|
+
| [Name] | Sponsor | Approver |
|
|
58
|
+
| [Name] | Lead Developer | Contributor |
|
|
59
|
+
|
|
60
|
+
## 7. Risks
|
|
61
|
+
| Risk | Probability | Impact | Mitigation |
|
|
62
|
+
|------|-------------|--------|------------|
|
|
63
|
+
| [Risk 1] | High | High | [Mitigation] |
|
|
64
|
+
|
|
65
|
+
## 8. Budget
|
|
66
|
+
| Category | Amount |
|
|
67
|
+
|----------|--------|
|
|
68
|
+
| Development | $X |
|
|
69
|
+
| Infrastructure | $Y |
|
|
70
|
+
| Total | $Z |
|
|
71
|
+
|
|
72
|
+
## 9. Approvals
|
|
73
|
+
| Name | Role | Date | Signature |
|
|
74
|
+
|------|------|------|-----------|
|
|
75
|
+
| [Name] | Sponsor | | |
|
|
76
|
+
| [Name] | PM | | |
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
---
|
|
80
|
+
|
|
81
|
+
## Sprint Planning Template
|
|
82
|
+
|
|
83
|
+
```markdown
|
|
84
|
+
# Sprint [N] Planning
|
|
85
|
+
|
|
86
|
+
**Sprint Duration**: [Start Date] - [End Date] (2 weeks)
|
|
87
|
+
**Sprint Goal**: [One sentence goal]
|
|
88
|
+
|
|
89
|
+
---
|
|
90
|
+
|
|
91
|
+
## Capacity
|
|
92
|
+
|
|
93
|
+
| Team Member | Capacity (days) | Notes |
|
|
94
|
+
|-------------|-----------------|-------|
|
|
95
|
+
| [Name] | 8 | PTO Friday |
|
|
96
|
+
| [Name] | 10 | Full capacity |
|
|
97
|
+
| **Total** | **18** | |
|
|
98
|
+
|
|
99
|
+
---
|
|
100
|
+
|
|
101
|
+
## Sprint Backlog
|
|
102
|
+
|
|
103
|
+
| ID | Story | Points | Assignee | Status |
|
|
104
|
+
|----|-------|--------|----------|--------|
|
|
105
|
+
| US-001 | [User story] | 5 | [Name] | To Do |
|
|
106
|
+
| US-002 | [User story] | 3 | [Name] | To Do |
|
|
107
|
+
| **Total** | | **8** | | |
|
|
108
|
+
|
|
109
|
+
---
|
|
110
|
+
|
|
111
|
+
## Technical Tasks
|
|
112
|
+
|
|
113
|
+
| Task | Story | Estimate | Assignee |
|
|
114
|
+
|------|-------|----------|----------|
|
|
115
|
+
| [Task 1] | US-001 | 4h | [Name] |
|
|
116
|
+
| [Task 2] | US-001 | 2h | [Name] |
|
|
117
|
+
|
|
118
|
+
---
|
|
119
|
+
|
|
120
|
+
## Dependencies
|
|
121
|
+
|
|
122
|
+
| Dependency | From | Status |
|
|
123
|
+
|------------|------|--------|
|
|
124
|
+
| [Dependency] | [Team/System] | Pending |
|
|
125
|
+
|
|
126
|
+
---
|
|
127
|
+
|
|
128
|
+
## Definition of Done
|
|
129
|
+
|
|
130
|
+
- [ ] Code complete and reviewed
|
|
131
|
+
- [ ] Tests written and passing
|
|
132
|
+
- [ ] Documentation updated
|
|
133
|
+
- [ ] Deployed to staging
|
|
134
|
+
- [ ] Product owner approved
|
|
135
|
+
```
|
|
136
|
+
|
|
137
|
+
---
|
|
138
|
+
|
|
139
|
+
## Status Report Template
|
|
140
|
+
|
|
141
|
+
```markdown
|
|
142
|
+
# Weekly Status Report
|
|
143
|
+
|
|
144
|
+
**Project**: [Project Name]
|
|
145
|
+
**Period**: [Start Date] - [End Date]
|
|
146
|
+
**Author**: [Name]
|
|
147
|
+
|
|
148
|
+
---
|
|
149
|
+
|
|
150
|
+
## Summary
|
|
151
|
+
|
|
152
|
+
🟢 On Track | 🟡 At Risk | 🔴 Off Track
|
|
153
|
+
|
|
154
|
+
**Overall Status**: 🟢
|
|
155
|
+
|
|
156
|
+
---
|
|
157
|
+
|
|
158
|
+
## Accomplishments This Week
|
|
159
|
+
|
|
160
|
+
- [Accomplishment 1]
|
|
161
|
+
- [Accomplishment 2]
|
|
162
|
+
- [Accomplishment 3]
|
|
163
|
+
|
|
164
|
+
---
|
|
165
|
+
|
|
166
|
+
## Planned for Next Week
|
|
167
|
+
|
|
168
|
+
- [ ] [Task 1]
|
|
169
|
+
- [ ] [Task 2]
|
|
170
|
+
- [ ] [Task 3]
|
|
171
|
+
|
|
172
|
+
---
|
|
173
|
+
|
|
174
|
+
## Metrics
|
|
175
|
+
|
|
176
|
+
| Metric | Target | Actual | Status |
|
|
177
|
+
|--------|--------|--------|--------|
|
|
178
|
+
| Sprint velocity | 30 pts | 28 pts | 🟢 |
|
|
179
|
+
| Bug count | < 5 | 3 | 🟢 |
|
|
180
|
+
| Test coverage | > 80% | 75% | 🟡 |
|
|
181
|
+
|
|
182
|
+
---
|
|
183
|
+
|
|
184
|
+
## Risks and Issues
|
|
185
|
+
|
|
186
|
+
### Risks
|
|
187
|
+
| Risk | Probability | Impact | Mitigation | Owner |
|
|
188
|
+
|------|-------------|--------|------------|-------|
|
|
189
|
+
| [Risk] | Medium | High | [Mitigation] | [Name] |
|
|
190
|
+
|
|
191
|
+
### Issues
|
|
192
|
+
| Issue | Impact | Action | Owner | Due |
|
|
193
|
+
|-------|--------|--------|-------|-----|
|
|
194
|
+
| [Issue] | [Impact] | [Action] | [Name] | [Date] |
|
|
195
|
+
|
|
196
|
+
---
|
|
197
|
+
|
|
198
|
+
## Blockers
|
|
199
|
+
|
|
200
|
+
- [ ] [Blocker 1] - Need [action] from [person]
|
|
201
|
+
|
|
202
|
+
---
|
|
203
|
+
|
|
204
|
+
## Resource Requests
|
|
205
|
+
|
|
206
|
+
- [Request 1]
|
|
207
|
+
```
|
|
208
|
+
|
|
209
|
+
---
|
|
210
|
+
|
|
211
|
+
## Meeting Notes Template
|
|
212
|
+
|
|
213
|
+
```markdown
|
|
214
|
+
# Meeting Notes
|
|
215
|
+
|
|
216
|
+
**Meeting**: [Meeting Name]
|
|
217
|
+
**Date**: YYYY-MM-DD HH:MM
|
|
218
|
+
**Attendees**: [Names]
|
|
219
|
+
**Facilitator**: [Name]
|
|
220
|
+
**Note Taker**: [Name]
|
|
221
|
+
|
|
222
|
+
---
|
|
223
|
+
|
|
224
|
+
## Agenda
|
|
225
|
+
|
|
226
|
+
1. [Topic 1] (10 min)
|
|
227
|
+
2. [Topic 2] (15 min)
|
|
228
|
+
3. [Topic 3] (10 min)
|
|
229
|
+
|
|
230
|
+
---
|
|
231
|
+
|
|
232
|
+
## Discussion Notes
|
|
233
|
+
|
|
234
|
+
### Topic 1: [Name]
|
|
235
|
+
- [Key point]
|
|
236
|
+
- [Key point]
|
|
237
|
+
- **Decision**: [Decision made]
|
|
238
|
+
|
|
239
|
+
### Topic 2: [Name]
|
|
240
|
+
- [Key point]
|
|
241
|
+
- **Decision**: [Decision made]
|
|
242
|
+
|
|
243
|
+
---
|
|
244
|
+
|
|
245
|
+
## Action Items
|
|
246
|
+
|
|
247
|
+
| Action | Owner | Due Date |
|
|
248
|
+
|--------|-------|----------|
|
|
249
|
+
| [Action 1] | [Name] | [Date] |
|
|
250
|
+
| [Action 2] | [Name] | [Date] |
|
|
251
|
+
|
|
252
|
+
---
|
|
253
|
+
|
|
254
|
+
## Decisions Made
|
|
255
|
+
|
|
256
|
+
1. [Decision 1]
|
|
257
|
+
2. [Decision 2]
|
|
258
|
+
|
|
259
|
+
---
|
|
260
|
+
|
|
261
|
+
## Next Meeting
|
|
262
|
+
|
|
263
|
+
**Date**: YYYY-MM-DD
|
|
264
|
+
**Topics**: [Topics for next meeting]
|
|
265
|
+
```
|
|
266
|
+
|
|
267
|
+
---
|
|
268
|
+
|
|
269
|
+
## Retrospective Template
|
|
270
|
+
|
|
271
|
+
```markdown
|
|
272
|
+
# Sprint [N] Retrospective
|
|
273
|
+
|
|
274
|
+
**Date**: YYYY-MM-DD
|
|
275
|
+
**Facilitator**: [Name]
|
|
276
|
+
**Participants**: [Names]
|
|
277
|
+
|
|
278
|
+
---
|
|
279
|
+
|
|
280
|
+
## What Went Well 👍
|
|
281
|
+
|
|
282
|
+
- [Item 1]
|
|
283
|
+
- [Item 2]
|
|
284
|
+
- [Item 3]
|
|
285
|
+
|
|
286
|
+
---
|
|
287
|
+
|
|
288
|
+
## What Could Be Improved 👎
|
|
289
|
+
|
|
290
|
+
- [Item 1]
|
|
291
|
+
- [Item 2]
|
|
292
|
+
- [Item 3]
|
|
293
|
+
|
|
294
|
+
---
|
|
295
|
+
|
|
296
|
+
## Action Items
|
|
297
|
+
|
|
298
|
+
| Action | Owner | Status |
|
|
299
|
+
|--------|-------|--------|
|
|
300
|
+
| [Action 1] | [Name] | Open |
|
|
301
|
+
| [Action 2] | [Name] | Open |
|
|
302
|
+
|
|
303
|
+
---
|
|
304
|
+
|
|
305
|
+
## Previous Action Items
|
|
306
|
+
|
|
307
|
+
| Action | Owner | Status |
|
|
308
|
+
|--------|-------|--------|
|
|
309
|
+
| [Previous action] | [Name] | ✅ Done |
|
|
310
|
+
| [Previous action] | [Name] | 🔄 In Progress |
|
|
311
|
+
|
|
312
|
+
---
|
|
313
|
+
|
|
314
|
+
## Team Health
|
|
315
|
+
|
|
316
|
+
| Category | Score (1-5) |
|
|
317
|
+
|----------|-------------|
|
|
318
|
+
| Collaboration | ⭐⭐⭐⭐ |
|
|
319
|
+
| Velocity | ⭐⭐⭐ |
|
|
320
|
+
| Quality | ⭐⭐⭐⭐ |
|
|
321
|
+
| Morale | ⭐⭐⭐⭐ |
|
|
322
|
+
```
|
|
323
|
+
|
|
324
|
+
---
|
|
325
|
+
|
|
326
|
+
## RACI Matrix Template
|
|
327
|
+
|
|
328
|
+
```markdown
|
|
329
|
+
# RACI Matrix
|
|
330
|
+
|
|
331
|
+
| Task | PM | Dev Lead | Developer | QA | Stakeholder |
|
|
332
|
+
|------|:--:|:--------:|:---------:|:--:|:-----------:|
|
|
333
|
+
| Requirements | A | C | I | C | R |
|
|
334
|
+
| Architecture | C | R | C | I | I |
|
|
335
|
+
| Development | I | A | R | C | I |
|
|
336
|
+
| Testing | I | C | C | R | I |
|
|
337
|
+
| Deployment | A | R | C | C | I |
|
|
338
|
+
| Sign-off | A | I | I | I | R |
|
|
339
|
+
|
|
340
|
+
**Legend**:
|
|
341
|
+
- **R** = Responsible (does the work)
|
|
342
|
+
- **A** = Accountable (final decision)
|
|
343
|
+
- **C** = Consulted (provides input)
|
|
344
|
+
- **I** = Informed (kept updated)
|
|
345
|
+
```
|
|
@@ -0,0 +1,219 @@
|
|
|
1
|
+
# QA Plan Template
|
|
2
|
+
|
|
3
|
+
## Overview
|
|
4
|
+
|
|
5
|
+
Template for creating comprehensive Quality Assurance plans.
|
|
6
|
+
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
## QA Plan Document
|
|
10
|
+
|
|
11
|
+
```markdown
|
|
12
|
+
# QA Plan: [Project/Feature Name]
|
|
13
|
+
|
|
14
|
+
## Document Information
|
|
15
|
+
|
|
16
|
+
| Field | Value |
|
|
17
|
+
|-------|-------|
|
|
18
|
+
| Version | 1.0 |
|
|
19
|
+
| Date | YYYY-MM-DD |
|
|
20
|
+
| Author | quality-assurance |
|
|
21
|
+
| Status | Draft / Approved |
|
|
22
|
+
| Reviewers | [Names] |
|
|
23
|
+
|
|
24
|
+
---
|
|
25
|
+
|
|
26
|
+
## 1. Introduction
|
|
27
|
+
|
|
28
|
+
### 1.1 Purpose
|
|
29
|
+
[Describe the purpose of this QA plan]
|
|
30
|
+
|
|
31
|
+
### 1.2 Scope
|
|
32
|
+
- **In Scope**: [What will be tested]
|
|
33
|
+
- **Out of Scope**: [What won't be tested]
|
|
34
|
+
|
|
35
|
+
### 1.3 References
|
|
36
|
+
- Requirements: [Link to requirements]
|
|
37
|
+
- Design: [Link to design docs]
|
|
38
|
+
- Related ADRs: [Links]
|
|
39
|
+
|
|
40
|
+
---
|
|
41
|
+
|
|
42
|
+
## 2. Test Strategy
|
|
43
|
+
|
|
44
|
+
### 2.1 Test Levels
|
|
45
|
+
|
|
46
|
+
| Level | Description | Tools |
|
|
47
|
+
|-------|-------------|-------|
|
|
48
|
+
| Unit | Individual functions/methods | Jest/pytest |
|
|
49
|
+
| Integration | Component interactions | Supertest |
|
|
50
|
+
| E2E | Full user journeys | Playwright |
|
|
51
|
+
| Performance | Load/stress testing | k6 |
|
|
52
|
+
| Security | Vulnerability testing | OWASP ZAP |
|
|
53
|
+
|
|
54
|
+
### 2.2 Test Types
|
|
55
|
+
|
|
56
|
+
- [ ] Functional Testing
|
|
57
|
+
- [ ] Regression Testing
|
|
58
|
+
- [ ] Smoke Testing
|
|
59
|
+
- [ ] Acceptance Testing
|
|
60
|
+
- [ ] Performance Testing
|
|
61
|
+
- [ ] Security Testing
|
|
62
|
+
- [ ] Accessibility Testing
|
|
63
|
+
|
|
64
|
+
### 2.3 Test Approach
|
|
65
|
+
|
|
66
|
+
**Test-First (Mandatory - Article III)**:
|
|
67
|
+
- All tests written before implementation
|
|
68
|
+
- Red-Green-Refactor cycle followed
|
|
69
|
+
|
|
70
|
+
**Integration-First (Article IX)**:
|
|
71
|
+
- Integration tests before unit tests
|
|
72
|
+
- E2E tests for critical paths
|
|
73
|
+
|
|
74
|
+
---
|
|
75
|
+
|
|
76
|
+
## 3. Test Environment
|
|
77
|
+
|
|
78
|
+
### 3.1 Environments
|
|
79
|
+
|
|
80
|
+
| Environment | Purpose | URL |
|
|
81
|
+
|-------------|---------|-----|
|
|
82
|
+
| Development | Developer testing | localhost |
|
|
83
|
+
| Staging | Integration testing | staging.example.com |
|
|
84
|
+
| Production | Live system | example.com |
|
|
85
|
+
|
|
86
|
+
### 3.2 Test Data
|
|
87
|
+
|
|
88
|
+
- **Strategy**: [Synthetic / Masked Production / Generated]
|
|
89
|
+
- **Reset Process**: [How test data is managed]
|
|
90
|
+
- **Sensitive Data**: [How handled]
|
|
91
|
+
|
|
92
|
+
---
|
|
93
|
+
|
|
94
|
+
## 4. Test Coverage Requirements
|
|
95
|
+
|
|
96
|
+
### 4.1 Coverage Targets
|
|
97
|
+
|
|
98
|
+
| Metric | Target | Current |
|
|
99
|
+
|--------|--------|---------|
|
|
100
|
+
| Line Coverage | 80% | - |
|
|
101
|
+
| Branch Coverage | 75% | - |
|
|
102
|
+
| Requirements Coverage | 100% | - |
|
|
103
|
+
|
|
104
|
+
### 4.2 Critical Paths
|
|
105
|
+
|
|
106
|
+
Must have 100% test coverage:
|
|
107
|
+
1. Authentication flow
|
|
108
|
+
2. Payment processing
|
|
109
|
+
3. User data operations
|
|
110
|
+
|
|
111
|
+
---
|
|
112
|
+
|
|
113
|
+
## 5. Entry/Exit Criteria
|
|
114
|
+
|
|
115
|
+
### 5.1 Entry Criteria
|
|
116
|
+
- [ ] Requirements approved
|
|
117
|
+
- [ ] Design complete
|
|
118
|
+
- [ ] Test environment ready
|
|
119
|
+
- [ ] Test data available
|
|
120
|
+
|
|
121
|
+
### 5.2 Exit Criteria
|
|
122
|
+
- [ ] All critical tests pass
|
|
123
|
+
- [ ] Coverage targets met
|
|
124
|
+
- [ ] No P1/P2 bugs open
|
|
125
|
+
- [ ] Performance targets met
|
|
126
|
+
- [ ] Security audit passed
|
|
127
|
+
|
|
128
|
+
---
|
|
129
|
+
|
|
130
|
+
## 6. Risk Assessment
|
|
131
|
+
|
|
132
|
+
| Risk | Probability | Impact | Mitigation |
|
|
133
|
+
|------|-------------|--------|------------|
|
|
134
|
+
| Tight timeline | High | High | Early testing, automation |
|
|
135
|
+
| Environment issues | Medium | High | Backup environments |
|
|
136
|
+
| Data quality | Medium | Medium | Data validation |
|
|
137
|
+
|
|
138
|
+
---
|
|
139
|
+
|
|
140
|
+
## 7. Schedule
|
|
141
|
+
|
|
142
|
+
| Phase | Start | End | Owner |
|
|
143
|
+
|-------|-------|-----|-------|
|
|
144
|
+
| Test Planning | MM/DD | MM/DD | QA Lead |
|
|
145
|
+
| Test Development | MM/DD | MM/DD | QA Team |
|
|
146
|
+
| Test Execution | MM/DD | MM/DD | QA Team |
|
|
147
|
+
| Bug Fixes | MM/DD | MM/DD | Dev Team |
|
|
148
|
+
| Regression | MM/DD | MM/DD | QA Team |
|
|
149
|
+
| Sign-off | MM/DD | MM/DD | QA Lead |
|
|
150
|
+
|
|
151
|
+
---
|
|
152
|
+
|
|
153
|
+
## 8. Deliverables
|
|
154
|
+
|
|
155
|
+
- [ ] Test Plan (this document)
|
|
156
|
+
- [ ] Test Cases
|
|
157
|
+
- [ ] Test Reports
|
|
158
|
+
- [ ] Bug Reports
|
|
159
|
+
- [ ] Coverage Reports
|
|
160
|
+
- [ ] Sign-off Document
|
|
161
|
+
|
|
162
|
+
---
|
|
163
|
+
|
|
164
|
+
## 9. Roles & Responsibilities
|
|
165
|
+
|
|
166
|
+
| Role | Responsibility | Person |
|
|
167
|
+
|------|----------------|--------|
|
|
168
|
+
| QA Lead | Plan, coordinate | [Name] |
|
|
169
|
+
| QA Engineer | Execute tests | [Name] |
|
|
170
|
+
| Developer | Fix bugs, unit tests | [Name] |
|
|
171
|
+
| PM | Review, approve | [Name] |
|
|
172
|
+
|
|
173
|
+
---
|
|
174
|
+
|
|
175
|
+
## 10. Tools
|
|
176
|
+
|
|
177
|
+
| Purpose | Tool |
|
|
178
|
+
|---------|------|
|
|
179
|
+
| Test Management | [Tool name] |
|
|
180
|
+
| Bug Tracking | [Tool name] |
|
|
181
|
+
| Automation | [Tool name] |
|
|
182
|
+
| CI/CD | [Tool name] |
|
|
183
|
+
| Coverage | [Tool name] |
|
|
184
|
+
|
|
185
|
+
---
|
|
186
|
+
|
|
187
|
+
## Appendix
|
|
188
|
+
|
|
189
|
+
### A. Test Case Template
|
|
190
|
+
[Link to template]
|
|
191
|
+
|
|
192
|
+
### B. Bug Report Template
|
|
193
|
+
[Link to template]
|
|
194
|
+
|
|
195
|
+
### C. Glossary
|
|
196
|
+
[Terms and definitions]
|
|
197
|
+
```
|
|
198
|
+
|
|
199
|
+
---
|
|
200
|
+
|
|
201
|
+
## Quick QA Checklist
|
|
202
|
+
|
|
203
|
+
### Before Development
|
|
204
|
+
- [ ] Requirements are testable (EARS format)
|
|
205
|
+
- [ ] Acceptance criteria defined
|
|
206
|
+
- [ ] Test environment ready
|
|
207
|
+
|
|
208
|
+
### During Development
|
|
209
|
+
- [ ] Tests written first
|
|
210
|
+
- [ ] CI/CD running tests
|
|
211
|
+
- [ ] Code review includes test review
|
|
212
|
+
|
|
213
|
+
### Before Release
|
|
214
|
+
- [ ] All tests passing
|
|
215
|
+
- [ ] Coverage targets met
|
|
216
|
+
- [ ] No critical bugs open
|
|
217
|
+
- [ ] Performance validated
|
|
218
|
+
- [ ] Security checked
|
|
219
|
+
- [ ] Stakeholder sign-off
|