Eighth graders learn that debugging is a process, not luck, from reproducing a bug and locating it to fixing it and testing the fix, and put the steps in order.
Students will be able to…
Debugging is a skill, not luck. What are the orderly steps that take you from “it doesn’t work” to a fix you can trust?
Project this and put the debugging steps in order — tap each step from reproducing the bug to testing the fix.
Tap any phase to open the teacher moves and student actions.
Your program runs but gives the wrong answer. Guessing wastes time. What is a smart, orderly way to track down the bug?
Students put the debugging steps in order.
Students debug a small program.
Students build a debugging log.
Students reflect on testing the fix.
Aligned to the CSTA K-12 Computer Science Standards and the ISTE Standards for Students.
Systematically test and refine programs.
Use a process to find and correct errors.
Document a program to make debugging easier.
Troubleshoot problems methodically.
Preview the three formative checks. Tap “Sample answer” to see what mastery looks like — hide them before you print for students.
Have students describe a bug, record each step they take to track it down, and note the fix and the test that proves it, building a habit of orderly debugging. A printable debugging worksheet is in the Computer Science library.
Tap a card to flip it, then rate whether you knew it. Built from this lesson’s vocabulary.
A quick self-check with instant feedback, drawn from this lesson’s key terms.
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.