Lesson Plan

Lesson Plan
Grade: Date: 18/01/2026
Subject: Computer Science
Lesson Topic: Show understanding of the need for a test strategy and test plan and their likely contents
Learning Objective/s:
  • Describe the purpose and benefits of a test strategy.
  • Identify the key components of a test strategy and a test plan.
  • Explain how entry and exit criteria guide testing phases.
  • Apply basic test‑design techniques to create simple test cases.
  • Evaluate metrics to assess testing effectiveness.
Materials Needed:
  • Projector or interactive whiteboard
  • Slide deck covering strategy and plan contents
  • Sample test‑plan template (printed handout)
  • Whiteboard and markers
  • Laptops with a document editor or IDE
  • Sticky notes for risk‑brainstorming
Introduction:
Begin with a quick poll: how many students have written a test case before? Review that testing must be systematic and aligned with project goals. Explain that by the end of the lesson they will be able to differentiate a test strategy from a test plan and outline their essential contents.
Lesson Structure:
  1. Do‑now (5') – Pairs list what “testing” means; share brief definitions.
  2. Mini‑lecture (10') – Present the need for a test strategy, its benefits, and typical contents (slides).
  3. Group activity (15') – Using a scenario, draft a brief test‑strategy outline with a provided template.
  4. Whole‑class debrief (5') – Groups present key points; teacher highlights alignment with objectives.
  5. Test‑plan deep dive (10') – Show detailed sections of a test plan and how it translates the strategy into actions.
  6. Hands‑on task (15') – Groups create a simple test plan for the same scenario, specifying entry/exit criteria and metrics.
  7. Quick check (5') – Exit ticket: write one difference between a test strategy and a test plan.
  8. Homework assignment (2') – Complete a full test‑case document for one module to bring to the next lesson.
Conclusion:
Summarise that a test strategy sets the vision while a test plan provides the roadmap for execution. Collect exit tickets and have students reflect on how entry/exit criteria safeguard testing phases. Remind them to finish the test‑case document for homework and be ready to discuss its results in the next class.