Lesson Plan

• Describe the four levels of testing (unit, integration, system, acceptance) and their purposes.
• Explain how to design effective test cases using required components (ID, steps, data, expected result).
• Apply appropriate test techniques (black‑box, white‑box, boundary, equivalence) to each testing level.
• Record and report test results using a test‑log format.
• Link testing activities to the stages of the systems life‑cycle.

• Projector and screen for slides
• Whiteboard and markers
• Student handouts summarising test levels and techniques
• Laptops with an IDE or testing tool installed
• Sample code modules for unit testing
• Test‑case worksheet and test‑log template
• Access to a sandbox test environment

Start with the question, “What could happen if we release software without testing?” Review the previous lesson on requirements analysis, then state today’s success criteria: students will differentiate testing levels, design valid test cases, and map testing activities onto the systems life‑cycle.

1. Do‑now (5’) – Students write three reasons why testing is essential on sticky notes and share.
2. Mini‑lecture (10’) – Overview of testing levels, purposes, and typical testers.
3. Guided activity (15’) – In pairs, create unit test cases for a supplied code module using the test‑case worksheet.
4. Demonstration (10’) – Teacher shows integration testing in the IDE, highlighting data‑flow checks.
5. Practice (15’) – Groups design integration test scenarios and record results in the test‑log template.
6. Whole‑class discussion (10’) – Link each testing activity to the corresponding phase of the systems life‑cycle diagram.
7. Exit ticket (5’) – Each student writes one key takeaway and one question they still have.

Recap the four testing levels and the importance of early, systematic testing. Collect exit tickets as a quick retrieval check. For homework, students will complete a full test plan (including test cases and a test log) for a simple calculator application.