Skip to content

Commit 68f5545

Browse files
committed
fix(build-and-test): compare test results against NFR targets
1 parent 11982b6 commit 68f5545

1 file changed

Lines changed: 8 additions & 0 deletions

File tree

aidlc-rules/aws-aidlc-rule-details/construction/build-and-test.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,12 @@ Analyze the project to determine appropriate testing strategy:
1919
- **Contract tests**: API contract validation between services
2020
- **Security tests**: Vulnerability scanning, penetration testing
2121

22+
When NFR Requirements defined measurable quality targets for any unit (e.g. test
23+
coverage thresholds, performance budgets), record those targets here. The summary
24+
in Step 7 MUST compare actual results against them and state whether each target
25+
was met. If a target was not met, the summary MUST say so explicitly and the
26+
"Ready for Operations" field MUST reflect it.
27+
2228
---
2329

2430
## Step 2: Generate Build Instructions
@@ -265,6 +271,8 @@ Create `aidlc-docs/construction/build-and-test/build-and-test-summary.md`:
265271
- **Passed**: [X]
266272
- **Failed**: [X]
267273
- **Coverage**: [X]%
274+
- **Coverage Target (from NFR Requirements)**: [X]% (or N/A if none defined)
275+
- **Target Met**: [Yes/No/N/A]
268276
- **Status**: [Pass/Fail]
269277

270278
### Integration Tests

0 commit comments

Comments
 (0)