Secure Software & Testing

Module 1 – Secure Software & Testing · 1

Page 3 of 3 · About 15 minutes per lesson, including practice.

Regression tests must challenge the fix

15-minute session: read for 3 minutes, trace for 3, experiment for 7, and complete the check for 2. Spend longer whenever you need.

Write a test that fails before a bug fix and passes afterward. Include the smallest input that reproduces the issue and a neighboring valid case. Keep authorization, boundary, and error-path tests; a happy-path screenshot is not sufficient. Document what your test cannot prove and avoid claiming absence of all vulnerabilities.

Practice and evidence: Predict the example or draw its state transitions. Change one assumption, test the boundary, and record the actual result. Explain what this small model does not establish about a production system.

Practice and evidence

Keep three notes: your prediction, the actual result, and why they match or differ. The completion check grades understanding; the practice task builds skill.

Example code on Agila Forge ↗