Everything you need before the bell rings
Learning Objectives
Students will be able to…
- ✓Follow a debugging process.
- ✓Reproduce and isolate a bug.
- ✓Change one thing at a time.
- ✓Verify the fix.
How do you find and fix a bug systematically?
Order the Debugging Process
Project this and have students put the debugging steps in order.
50 minutes, five moves
Tap any phase to open the teacher moves and student actions.
Hook — It Worked Yesterday!
What do you do when your program suddenly breaks?
👩🏫 Teacher Moves
- Show a buggy program.
- Ask how to start.
- Set the goal.
🎒 Student Actions
- Look.
- Guess.
- Get ready.
Use — Debugging Strategies
Students use the process.
👩🏫 Teacher Moves
- Send students to Order the Debugging Process.
- Order the steps.
- Note change one thing at a time.
🎒 Student Actions
- Order.
- Say.
- Note it.
Modify — Narrow It Down
Students modify.
👩🏫 Teacher Moves
- Add a print to inspect a value.
- Comment out a section.
- Isolate the broken line.
🎒 Student Actions
- Print.
- Comment.
- Isolate.
Create — Fix & Verify
Students create.
👩🏫 Teacher Moves
- Fix a provided bug.
- Test the fix.
- Check nothing else broke.
🎒 Student Actions
- Fix.
- Test.
- Check.
Reflect — Reflect
Students close.
👩🏫 Teacher Moves
- Name the first step.
- Say why change one thing.
- Complete the exit ticket.
🎒 Student Actions
- Name it.
- Say.
- 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 refine programs.
Document programs to make them easier to follow.
Systematically identify and fix problems.
Test and refine solutions.
One lesson, every learner
Multilingual Learners
- Debug-step cards.
- Frame: “what, where, why, fix, check.”
- Think-aloud a fix.
Support & Access
- Use 3 steps.
- Fix one simple bug.
- Use a checklist.
Stretch & Extend
- Use a debugger’s breakpoints.
- Write a bug report.
- Add tests to prevent regressions.
What to gather
- 📽️Screen / board
- 🐛Debug-step cards
- 💻Order the Debugging Process
- 🐍A buggy program
- 📓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: debugging strategies.
Have students list the debugging steps in order. A printable debugging worksheet is in the Computer Science 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
- an error that makes a program misbehave
- to make the bug happen again
- a fix that breaks something else
- to find and fix bugs
- to confirm it is truly fixed
- a guess about the cause
- to check if a change worked
- to narrow down where it occurs
Part B · Show what you learned
- What is the first debugging step?
- Why change one thing at a time?
- What is the last step?
Part B: 1) Reproduce the bug (make it happen again). 2) So you know exactly what fixed it. 3) Verify the fix and that nothing else broke.