Learning objective
Debugging
Debugging & Error Resolution
1
2
3
4
5
6
Master systematic techniques to find, isolate, and fix logic, syntax, and runtime errors in programs.
Spotting Errors
Identify and fix simple errors in physical sequences and robot paths.
Let's Go!
Learn
Compare a broken sequence where a sprite turns the wrong way with a corrected sequence.
Volcanoes: Earth's Fiery Chimneys!
Melted subterranean rock called magma rises through vents. When it erupts onto the surface, it becomes glowing red lava!
🌋🔥
My Study Notes
Try it yourself
Spot the Bug
🚀 Open a practice space
Or try locally: 🍓 Raspberry Pi Projects
🌟 Student Project GuideSuccess Criteria & WAGOLL (What A Good One Looks Like)
🎯 Task Success Criteria (Rubric)
Foundation
Notices when a physical robot or sprite stops at the wrong location.
Developing
Identifies which single step in a 3-step sequence caused the mistake.
Secure (Goal)
Corrects the erroneous step to ensure the sequence finishes successfully.
Mastery
Explains why the original step caused an error and demonstrates the fix.
👀 What A Good One Looks Like (WAGOLL)
Exemplar Standard
A top-tier student project for Spotting Errors includes:
- Core Deliverable: Spot the Bug
- Target Quality: Corrects the erroneous step to ensure the sequence finishes successfully.
- Excellence & Polish: Explains why the original step caused an error and demonstrates the fix.
📁
Save to Your Website Portfolio:
When you finish creating your project in your software, copy the share link or take a screenshot and publish it onto your student portfolio website!
⭐Self-Assessment: How confident do you feel with this skill?
Reflect
Learning check
Teacher setup, curriculum links and progress descriptors
Spark support
Routine: See Think Wonder
Achievement pathway
- Foundation: Notices when a physical robot or sprite stops at the wrong location.
- Developing: Identifies which single step in a 3-step sequence caused the mistake.
- Secure: Corrects the erroneous step to ensure the sequence finishes successfully.
- Mastering: Explains why the original step caused an error and demonstrates the fix.
Curriculum links
Curriculum strand: algorithms-programming
Outcome: AP.01.B.1.1 — Identify and fix simple errors in physical sequences and robot paths.
PYP: Form · Digital instructions must be precise for systems to work as expected.
Learner profile: Inquirer
Competency tags
Gate support
Accessibility alternative:
Teacher override: allow
Locked level
Level 2: Step Tracing
Complete the previous learning check to unlock this next level.
Step Tracing
Predict program behavior by tracing execution step-by-step.
Learning objective
Trace code line-by-line or block-by-block to predict where a bug occurs.
Let's Go!
Learn
Use a step-execution tool to run code one block at a time.
📁 Source Document
➔
📋 Destination Notepad
Try it yourself
Trace the Code
🚀 Open a practice space
Or try locally: 🍓 Raspberry Pi Projects
🌟 Student Project GuideSuccess Criteria & WAGOLL (What A Good One Looks Like)
🎯 Task Success Criteria (Rubric)
Foundation
Follows along as code blocks highlight during execution.
Developing
Predicts where a character will land after each individual block runs.
Secure (Goal)
Traces a 5-block script manually and highlights the exact block containing the bug.
Mastery
Teaches a partner how to step through code block-by-block to find hidden bugs.
👀 What A Good One Looks Like (WAGOLL)
Exemplar Standard
A top-tier student project for Step Tracing includes:
- Core Deliverable: Trace the Code
- Target Quality: Traces a 5-block script manually and highlights the exact block containing the bug.
- Excellence & Polish: Teaches a partner how to step through code block-by-block to find hidden bugs.
📁
Save to Your Website Portfolio:
When you finish creating your project in your software, copy the share link or take a screenshot and publish it onto your student portfolio website!
⭐Self-Assessment: How confident do you feel with this skill?
Reflect
Learning check
Teacher setup, curriculum links and progress descriptors
Spark support
Routine: Zoom In
Achievement pathway
- Foundation: Follows along as code blocks highlight during execution.
- Developing: Predicts where a character will land after each individual block runs.
- Secure: Traces a 5-block script manually and highlights the exact block containing the bug.
- Mastering: Teaches a partner how to step through code block-by-block to find hidden bugs.
Curriculum links
Curriculum strand: algorithms-programming
Outcome: AP.01.B.1.1 — Predict program behavior by tracing execution step-by-step.
PYP: Function · Tracing code step-by-step reveals where intent diverges from execution.
Learner profile: Communicator
Competency tags
Gate support
Accessibility alternative:
Teacher override: allow
Locked level
Level 3: Logic vs Syntax
Complete the previous learning check to unlock this next level.
Logic vs Syntax
Distinguish between syntax errors and logical errors in block programs.
Learning objective
Classify bugs as syntax errors (invalid structure) or logic errors (unexpected outcome).
Let's Go!
Learn
Compare a script with a broken snap connection to a script with `score = score - 1`.
Volcanoes: Earth's Fiery Chimneys!
Melted subterranean rock called magma rises through vents. When it erupts onto the surface, it becomes glowing red lava!
🌋🔥
My Study Notes
Try it yourself
Classify and Fix
🚀 Open a practice space
Or try locally: 🍓 Raspberry Pi Projects
🌟 Student Project GuideSuccess Criteria & WAGOLL (What A Good One Looks Like)
🎯 Task Success Criteria (Rubric)
Foundation
Recognizes when code fails to run versus when code runs but gives wrong output.
Developing
Distinguishes an unattached block (syntax) from a wrong math operator (logic).
Secure (Goal)
Categorizes a list of 6 bugs as either syntax or logic errors and resolves both types.
Mastery
Analyzes complex scripts and explains how syntax and logic errors interact.
👀 What A Good One Looks Like (WAGOLL)
Exemplar Standard
A top-tier student project for Logic vs Syntax includes:
- Core Deliverable: Classify and Fix
- Target Quality: Categorizes a list of 6 bugs as either syntax or logic errors and resolves both types.
- Excellence & Polish: Analyzes complex scripts and explains how syntax and logic errors interact.
📁
Save to Your Website Portfolio:
When you finish creating your project in your software, copy the share link or take a screenshot and publish it onto your student portfolio website!
⭐Self-Assessment: How confident do you feel with this skill?
Reflect
Learning check
Teacher setup, curriculum links and progress descriptors
Spark support
Routine: See Think Wonder
Achievement pathway
- Foundation: Recognizes when code fails to run versus when code runs but gives wrong output.
- Developing: Distinguishes an unattached block (syntax) from a wrong math operator (logic).
- Secure: Categorizes a list of 6 bugs as either syntax or logic errors and resolves both types.
- Mastering: Analyzes complex scripts and explains how syntax and logic errors interact.
Curriculum links
Curriculum strand: algorithms-programming
Outcome: AP.02.B.1.1 — Distinguish between syntax errors and logical errors in block programs.
PYP: Connection · Programs fail differently depending on whether rules were broken or logic was flawed.
Learner profile: Thinker
Competency tags
Gate support
Accessibility alternative:
Teacher override: allow
Locked level
Level 4: Isolation Methods
Complete the previous learning check to unlock this next level.
Isolation Methods
Apply systematic isolation techniques like disabling blocks and speech-bubble printouts.
Learning objective
Isolate problematic code sections using temporary block disconnection and variable say blocks.
Let's Go!
Learn
Debug a multi-sprite project by testing each sprite's script independently.
Homework.docx
Puppy.jpg
Story_Chapter1.txt
Class_Anthem.mp3
Field_Trip.png
Try it yourself
Isolate and Resolve
🚀 Open a practice space
Or try locally: 🍓 Raspberry Pi Projects
🌟 Student Project GuideSuccess Criteria & WAGOLL (What A Good One Looks Like)
🎯 Task Success Criteria (Rubric)
Foundation
Disconnects blocks randomly when trying to fix a bug.
Developing
Disconnects specific script sections systematically to test modules in isolation.
Secure (Goal)
Uses 'say variable' blocks and temporary script detachment to pinpoint the exact broken block.
Mastery
Develops a structured 4-step debugging protocol for team coding projects.
👀 What A Good One Looks Like (WAGOLL)
Exemplar Standard
A top-tier student project for Isolation Methods includes:
- Core Deliverable: Isolate and Resolve
- Target Quality: Uses 'say variable' blocks and temporary script detachment to pinpoint the exact broken block.
- Excellence & Polish: Develops a structured 4-step debugging protocol for team coding projects.
📁
Save to Your Website Portfolio:
When you finish creating your project in your software, copy the share link or take a screenshot and publish it onto your student portfolio website!
⭐Self-Assessment: How confident do you feel with this skill?
Reflect
Learning check
Teacher setup, curriculum links and progress descriptors
Spark support
Routine: ShortcutSimulator
Achievement pathway
- Foundation: Disconnects blocks randomly when trying to fix a bug.
- Developing: Disconnects specific script sections systematically to test modules in isolation.
- Secure: Uses 'say variable' blocks and temporary script detachment to pinpoint the exact broken block.
- Mastering: Develops a structured 4-step debugging protocol for team coding projects.
Curriculum links
Curriculum strand: algorithms-programming
Outcome: AP.02.B.1.1 — Apply systematic isolation techniques like disabling blocks and speech-bubble printouts.
PYP: Change · Isolating code components systematically exposes hidden errors.
Learner profile: Principled
Competency tags
Gate support
Accessibility alternative:
Teacher override: allow
Locked level
Level 5: Edge Case Testing
Complete the previous learning check to unlock this next level.
Edge Case Testing
Design test cases that include normal, boundary, and edge case inputs.
Learning objective
Create comprehensive test tables covering standard inputs, zero values, negative numbers, and rapid inputs.
Let's Go!
Learn
Learn how boundary values (0, max values, empty inputs) stress-test code logic.
Try it yourself
Build a Test Matrix
🚀 Open a practice space
Or try locally: 🍓 Raspberry Pi Projects
🌟 Student Project GuideSuccess Criteria & WAGOLL (What A Good One Looks Like)
🎯 Task Success Criteria (Rubric)
Foundation
Tests programs using only standard positive inputs.
Developing
Identifies obvious edge cases like zero or negative user input.
Secure (Goal)
Constructs a complete test matrix with boundary inputs, unexpected characters, and concurrent events.
Mastery
Evaluates third-party programs by conducting rigorous stress-testing and edge-case audits.
👀 What A Good One Looks Like (WAGOLL)
Exemplar Standard
A top-tier student project for Edge Case Testing includes:
- Core Deliverable: Build a Test Matrix
- Target Quality: Constructs a complete test matrix with boundary inputs, unexpected characters, and concurrent events.
- Excellence & Polish: Evaluates third-party programs by conducting rigorous stress-testing and edge-case audits.
📁
Save to Your Website Portfolio:
When you finish creating your project in your software, copy the share link or take a screenshot and publish it onto your student portfolio website!
⭐Self-Assessment: How confident do you feel with this skill?
Reflect
Learning check
Teacher setup, curriculum links and progress descriptors
Spark support
Routine: See Think Wonder
Achievement pathway
- Foundation: Tests programs using only standard positive inputs.
- Developing: Identifies obvious edge cases like zero or negative user input.
- Secure: Constructs a complete test matrix with boundary inputs, unexpected characters, and concurrent events.
- Mastering: Evaluates third-party programs by conducting rigorous stress-testing and edge-case audits.
Curriculum links
Curriculum strand: algorithms-programming
Outcome: AP.03.B.1.1 — Design test cases that include normal, boundary, and edge case inputs.
PYP: Perspective · Robust software requires rigorous testing against extreme and unexpected inputs.
Learner profile: Knowledgeable
Competency tags
Gate support
Accessibility alternative:
Teacher override: allow
Locked level
Level 6: Console & Stack Traces
Complete the previous learning check to unlock this next level.
Console & Stack Traces
Interpret text console error logs, line numbers, and stack traces to fix complex programs.
Learning objective
Read error messages and stack traces to identify line numbers and error types in text-based or block code.
Let's Go!
Learn
Deconstruct stack trace structures: Error Name, Description, File Name, and Line Number.
Try it yourself
Console Diagnostics
🚀 Open a practice space
Or try locally: 🍓 Raspberry Pi Projects
🌟 Student Project GuideSuccess Criteria & WAGOLL (What A Good One Looks Like)
🎯 Task Success Criteria (Rubric)
Foundation
Gives up when seeing a text error message or console log.
Developing
Reads the line number provided in an error message to locate the fault.
Secure (Goal)
Interprets stack traces, identifies exception types (e.g., IndexOutOfBounds, TypeError), and fixes runtime faults.
Mastery
Mentors peers in reading developer tools, network logs, and console outputs for full-stack debugging.
👀 What A Good One Looks Like (WAGOLL)
Exemplar Standard
A top-tier student project for Console & Stack Traces includes:
- Core Deliverable: Console Diagnostics
- Target Quality: Interprets stack traces, identifies exception types (e.g., IndexOutOfBounds, TypeError), and fixes runtime faults.
- Excellence & Polish: Mentors peers in reading developer tools, network logs, and console outputs for full-stack debugging.
📁
Save to Your Website Portfolio:
When you finish creating your project in your software, copy the share link or take a screenshot and publish it onto your student portfolio website!
⭐Self-Assessment: How confident do you feel with this skill?
Reflect
Learning check
Teacher setup, curriculum links and progress descriptors
Spark support
Routine: Zoom In
Achievement pathway
- Foundation: Gives up when seeing a text error message or console log.
- Developing: Reads the line number provided in an error message to locate the fault.
- Secure: Interprets stack traces, identifies exception types (e.g., IndexOutOfBounds, TypeError), and fixes runtime faults.
- Mastering: Mentors peers in reading developer tools, network logs, and console outputs for full-stack debugging.
Curriculum links
Curriculum strand: algorithms-programming
Outcome: AP.03.B.1.1 — Interpret text console error logs, line numbers, and stack traces to fix complex programs.
PYP: Reflection · Developer diagnostics and error logs provide precise maps to software fixes.
Learner profile: Reflective
Competency tags
Gate support
Accessibility alternative:
Teacher override: allow