Testing — Functionality Test Plan
intermediate20 minLearning objectives
- Create a test plan covering links, user interactivity and responsiveness
- Execute the test plan and capture evidence (screenshots / screen recordings)
Learn
C3 — Planning and executing functionality tests
A test plan turns "I think it works" into evidence a marker (or a real client) can actually check. For each test, record:
| Test # | What's being tested | Test data / steps | Expected outcome | Actual outcome | Pass/Fail |
|---|---|---|---|---|---|
| 1 | Home → Products link | Click "Products" in nav from Home | Products page loads | Products page loaded | Pass |
| 2 | Enquiry form validation | Submit form with empty "email" field | Error message shown, form not submitted | Error message shown correctly | Pass |
| 3 | Responsive layout | Resize browser to 375px width | Navigation collapses to hamburger menu | Navigation stayed full-width, overlapping content | Fail |
What to cover
- Links — every internal and external link goes where it should.
- User interactivity — forms validate correctly, sliders/galleries/JavaScript features behave as designed, buttons do what they claim to.
- Responsiveness — the layout holds up correctly across common screen sizes, not just your own device.
Capturing evidence
A screenshot (or short screen recording) alongside each test row shows the actual outcome, not just your written claim — this is what PSAB Task 3 needs as evidence of testing.
Task
Build a test plan covering at least 8 tests across links, interactivity and responsiveness for your own site. Execute every test, record the actual outcome, and capture evidence for each.
Log in to track this lesson on your progress dashboard.
Log in