Capstone test oracles and defect evidence
This required 22–32-hour integrated package strengthens the existing guided labs. Allocation: lessons/predictions 5–7 hours, implementation/testing 11–17, assessment/repair 6–8. Author estimates require learner timing pilots and are included in the semester workload contract. Reuse the same service and evidence; avoid creating a second portfolio.
Prerequisite bridge
Bring the preceding module's implementation, risk record and failure observations. Separate assumptions, model results and actual runtime evidence. Review the specific prerequisite named in each lesson before its exercise. Missing runtime tools leave execution evidence pending; a written prediction is not an executed experiment.
Lesson sequence
- Test the claim with an independent oracle.
- Preserve the failing schedule before repairing a defect.
- Keep mocks from proving their own assumptions.
Integrated experiment
Reuse the walking skeleton, risk matrix, defect clinic and maintainability review. Add an oracle/fault-sensitivity record for the highest-risk invariant, one reproducible interleaving or failure cut, and a mock-boundary audit. Show the system working after the repair, not only a unit test passing. Keep any seeded fault explicitly labeled and preserve independent review evidence for the final code changes.
Complete the assessment. Original guided labs, security controls, deployment/testing and peer requirements remain mandatory. Use synthetic data and a disposable local environment where supported; no cloud purchase is required by this extension.
Selective resources
SRE testing chapter; Google code review. Prior semester testing and concurrency labs remain the backbone.