Third graders learn that every coder makes mistakes — and fixing them is called debugging. You run the program, find the step that goes wrong, fix it, and run it again. They order the steps, then fix a mistake in a program.
Students will be able to…
What do you do when your code does not work?
Project this and have students put the steps for fixing a mistake in order.
Tap any phase to open the teacher moves and student actions.
What do you do when your program does the wrong thing?
Students use the steps.
Students modify.
Students create.
Students close.
Aligned to the CSTA K-12 Computer Science Standards and the ISTE Standards for Students.
Test and debug a program to make sure it runs.
Create programs with sequences & loops.
Decompose a problem to find the bug.
Test and fix solutions.
Preview the three formative checks. Tap “Sample answer” to see what mastery looks like — hide them before you print for students.
Have students list the steps to fix a mistake. 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.