Outcomes
What students should leave with
- Differentiate manual checks, automated tests, and exploratory review work.
- Plan a practical regression set for UI and API behavior.
- Use test evidence to support safer merges and releases.
Reference map
Core topics to cover
Test strategy
Regression coverage
UI checks
API checks
Bug reporting
CI test gates
Release evidence
Module sequence
ICCT lesson flow
Module 1
Testing with intention
Lessons: 2
Choose the right kind of testing for the risk in front of you.
Manual, exploratory, and automated checks
when each approach provides the most value
Risk-based test planning
focusing effort where breakage matters most
Checkpoint lab
Plan a test strategy for a student portal update and explain which flows must be protected first.
Module 2
Automating the right layer
Lessons: 2
Keep automation useful by matching it to stable, high-value behavior.
UI automation basics
critical user paths, selectors, and durable assertions
API checks and service confidence
validating contracts and response behavior
Checkpoint lab
Design a smoke suite that covers login, form submission, and one API-backed listing flow.
Module 3
Evidence and release readiness
Lessons: 2
Turn test work into something teams can act on.
Bug reports and reproduction steps
writing findings that teammates can fix quickly
CI gates and release summaries
communicating what passed, what failed, and what remains risky
Checkpoint lab
Prepare a release-quality summary for a feature branch with pass/fail notes and open concerns.
Capstone prompts
Projects students can actually ship
Regression Pack Starter
Build a focused test pack for the highest-risk flows in an internal application.
API Smoke Suite Plan
Define the endpoints, assertions, and release conditions for a lightweight API confidence check.