Lesson Plan

• Describe why selecting appropriate test data is essential for effective test plans.
• Apply equivalence partitioning and boundary value analysis to identify representative test inputs.
• Construct decision tables and state‑transition tests to cover logical and state‑based scenarios.
• Prioritise and document test data in a test plan using clear identifiers.

• Projector or interactive whiteboard
• Slide deck covering test‑data techniques
• Sample “Student Grade” program source code
• Worksheets with EP/BVA tables
• Test‑plan template handout
• Laptops with an IDE or code editor

Begin with a quick poll: “What makes a test case useful?” Connect responses to the idea of efficient test‑data selection. Review the previous lesson on writing test cases. Explain that today’s success criteria are to choose and document test data using recognised techniques.

1. Do‑now (5'): Students list three reasons why test data matters on sticky notes.
2. Mini‑lecture (10'): Overview of EP and BVA with simple numeric examples.
3. Guided practice (12'): Work through the “Student Grade” program, filling an EP/BVA table as a class.
4. Group activity (15'): Teams create a decision table for the “late submission” extension and share findings.
5. State‑transition demo (8'): Show a flowchart and map test cases to transitions.
6. Documentation sprint (10'): Students record selected test data in the provided test‑plan template, prioritising high‑risk cases.
7. Check for understanding (5'): Quick quiz via Kahoot! covering key techniques.

Recap the four techniques and how they fit into a systematic test plan. Students complete an exit ticket: “Write one test‑data example for a new feature and state which technique you used.” Assign homework to apply EP and BVA to a personal coding project and bring the completed table to the next class.