Capstone brief: Band 3
Evidence 16 for Module 16. Hours 230.5–268. Assessed at Gate 4.
| Field | Value |
|---|---|
| Track | Band 3 |
| Band | 3 |
| UK GDaD PCF role | Quality assurance test analyst or Test engineer, associate level |
| Module 16 depth | Apply with support |
| Automation target | Awareness |
| Presentation | 10 minutes, aimed at a non-technical audience |
The capstone, from the spec
Triage one week of CI results and raise defects; write 5 Given-When-Then scenarios; make 2 reviewed changes to existing tests.
Scope
One week of CI results for your team's existing automated suite, and 5 manual cases from your Evidence 7 sample that are marked to automate.
Agree the exact scope with the product owner and mentor at hour 230.5, using the scope agreement, your Evidence 7 analysis, and your Evidence 15 estimate.
Deliverables
- A triage record (Module 13 template) for every failure in one week of CI runs, with defects raised for product defects.
- 5 Given-When-Then scenarios, reviewed and agreed by the product owner, with synthetic data named.
- 2 changes to existing tests, each through a pull request reviewed by a developer or the mentor. For example, updating an expected value after an agreed change, or replacing a brittle locator.
- Traceability rows (Module 14 template) for the 5 scenarios, where they protect a hazard.
Acceptance
The product owner and the Gate 4 panel will look for:
- Every failure in the week is triaged with the right kind and a reason.
- Each scenario has checkable Then lines and is agreed by the product owner.
- Both changes are merged and the suite is green after them.
- Synthetic data only, and no secrets in source control.
- You can explain every line you submitted.
Support
The mentor may pair with you on the code changes. You make the triage decisions and write the scenarios.
Presentation
10 minutes, plus questions, following the presentation outline. Include a live run: it is the Gate 4 Part D practical.
Panel
Chair: a lead test engineer or test manager at least one band above you, not your mentor. A developer from another team. The training lead. The clinical safety officer reviews traceability evidence in writing.
Gate 4 thresholds
At least 90% in each of Parts A, B, and C of the capability self-assessment; Part D Meets; no skill more than one level below expected; test engineering at your automation target; capstone accepted by the product owner. See the spec for the full rules.
View this document on GitHub materials/modules/module-16-capstone/brief-band-3.md