Everything you need before the bell rings
Learning Objectives
Students will be able to…
- ✓Write test cases.
- ✓Cover edge cases.
- ✓Run tests & fix.
- ✓Re-test.
How do you make sure your code actually works — in every case?
Order the Testing Steps
Project this and have students put the testing steps in order.
50 minutes, five moves
Tap any phase to open the teacher moves and student actions.
Hook — Does It Work?
Your code runs once — but does it work for ALL inputs?
👩🏫 Teacher Moves
- Pose the question.
- Share ideas.
- Set the goal.
🎒 Student Actions
- Think.
- Share.
- Get ready.
Use — Testing
Students learn.
👩🏫 Teacher Moves
- Send students to Order the Testing Steps.
- Order the steps.
- Note include edge cases.
🎒 Student Actions
- Order.
- Say.
- Note it.
Modify — Test It
Students practice.
👩🏫 Teacher Moves
- List normal test cases.
- Add an edge case.
- Predict each result.
🎒 Student Actions
- List.
- Edge.
- Predict.
Create — Create
Students apply.
👩🏫 Teacher Moves
- Test a small program.
- Fix a failure.
- Re-test it.
🎒 Student Actions
- Test.
- Fix.
- Re-test.
Reflect — Reflect
Students close.
👩🏫 Teacher Moves
- What is an edge case?
- Why re-test after a fix?
- Complete the exit ticket.
🎒 Student Actions
- Say it.
- Say it.
- Complete the exit ticket.
Built to the standards you report on
Aligned to the CSTA K-12 Computer Science Standards and the ISTE Standards for Students.
Systematically test and debug programs.
Evaluate correctness with test cases.
Develop and test as a process.
Verify computational solutions.
One lesson, every learner
Multilingual Learners
- Testing-step cards.
- Frame: "an edge case is ___."
- Test a tiny program.
Support & Access
- Use 3 core steps.
- Use one normal test.
- Use a template.
Stretch & Extend
- Write automated tests.
- Add boundary cases.
- Test a partner’s code.
What to gather
- 📽️Screen / board
- 🧪Testing cards
- 💻Order the Testing Steps
- 📋Test-case worksheet
- 📓Notebooks
- 🎫Exit-ticket slips
Key terms — hover for a quick definition
Exit Ticket
Preview the three formative checks. Tap “Sample answer” to see what mastery looks like — hide them before you print for students.
Reflect: testing & test cases.
Have students write test cases for a small program. A printable test-case worksheet is in the CS library.
Study the key terms
Tap a card to flip it, then rate whether you knew it. Built from this lesson’s vocabulary.
Nice work!
Check your understanding
A quick self-check with instant feedback, drawn from this lesson’s key terms.
Nice work!
Printable worksheet
A print-and-go review sheet with a built-in answer key. Tap “Show answer key” to reveal answers, or print the clean version for students.
Part A · Write the word that matches each meaning
- test again after a fix
- how much is tested
- an error in code
- what should happen
- whether a test succeeds
- find and fix a bug
- an input and its expected result
- an unusual or extreme input
Part B · Show what you learned
- What is an edge case?
- Why re-test after fixing a bug?
- When should you think up test cases?
Part B: 1) An unusual or extreme input, like an empty list. 2) To confirm the fix worked and nothing else broke. 3) Before and while you code — not just at the end.