Lesson Plan

• Describe the main test design techniques (black‑box, white‑box, boundary value, equivalence partitioning, decision table).
• Explain the hierarchy of test strategies (unit, integration, system, acceptance) and when each is applied.
• Construct a simple test plan entry that records test data, expected outcome, actual outcome and remedial action.
• Analyse test results to identify defects and outline the remedial‑re‑testing cycle.

• Projector and screen
• Computer lab with IDE or web application for demo
• Printed handout of sample test plan table
• Worksheet with test case scenarios
• Sticky notes or index cards for defect logging

Begin with a quick poll: “What happens when a new app crashes on launch?” Use the responses to highlight the need for systematic testing. Review the previous lesson on system implementation and link it to today’s focus on verifying that work. State that by the end of class students will be able to design test cases and complete a test‑plan entry.

1. Do‑Now (5’): Students list common software bugs they have encountered; share briefly.
2. Mini‑lecture (10’): Overview of test designs and strategies with real‑world examples.
3. Guided practice (15’): In pairs, students create test cases for a login screen using black‑box and boundary value techniques; teacher circulates.
4. Hands‑on activity (15’): Complete a sample test‑plan table on the worksheet, recording test data, expected and actual outcomes, and remedial actions.
5. Defect‑logging simulation (10’): Groups role‑play logging a failed test, assigning a fix, and re‑testing; discuss the cycle.
6. Check for understanding (5’): Quick quiz via Kahoot/exit ticket asking key definitions.

Summarise how test designs, strategies, and a structured test plan work together to ensure software quality. Students submit an exit ticket naming one test design they will use in their next project. Assign homework: draft a test plan for a simple calculator program covering at least three test cases.