Lesson Plan

Lesson Plan
Grade: Date: 01/12/2025
Subject: Information Communication Technology ICT
Lesson Topic: Know and understand the need to test the system before implementation
Learning Objective/s:
  • Describe why testing is essential before system implementation.
  • Identify and differentiate key testing types (unit, integration, system, UAT) and approaches (black‑box, white‑box, grey‑box).
  • Create a basic test plan that includes objectives, test cases, schedule, and defect‑logging procedures.
  • Execute sample test cases and interpret results to determine pass/fail status.
  • Evaluate the impact of inadequate testing on project cost, schedule, and stakeholder confidence.
Materials Needed:
  • Projector and screen
  • Whiteboard and markers
  • Printed handout of sample test case table
  • Laptop with IDE or simulation software
  • Test plan template worksheet
  • Sample application for testing (e.g., login module)
Introduction:
Begin with a quick scenario: a new school management system crashes on launch because it wasn’t tested. Ask learners to recall any real‑world example where lack of testing caused problems. Explain that today they will learn the purpose of testing, key test types, and how to produce a simple test plan – the success criteria for the lesson.
Lesson Structure:
  1. Do‑now (5') – students write down a recent news story about software failure due to poor testing.
  2. Mini‑lecture (10') – teacher explains why testing is needed and where it fits in the systems life cycle.
  3. Interactive activity (10') – groups match testing types and approaches to definitions using cards.
  4. Demonstration (10') – teacher walks through a sample test case (login) on the laptop, showing expected vs. actual results.
  5. Guided practice (15') – students fill out a test plan worksheet for a simple calculator module, create test cases, and record results.
  6. Check for understanding (5') – quick quiz (e.g., Kahoot) on key concepts; collect worksheets for feedback.
Conclusion:
Summarise that testing safeguards quality, reduces costs, and builds user confidence. Students complete an exit ticket by writing one benefit of testing and one risk of skipping it. Assign homework to draft a test plan for a chosen everyday device or app.