Bugs
Intro to Python Programming Grades 9–12 3-day lesson 27 deliverables Help students find and fix Python bugs by reading what the program actually does. Students sort programming tasks, tell error types apart and use bug tickets to compare expected and actual results. They repair short programs, explain how they recognized each error and test a badge program with different user answers.
● Instant download · Lifetime access · Editable & print-ready
Print + digitalPDF, PowerPoint, Word & Google
Answer keysA key for every page
Built-in assessmentExit tickets + lesson quiz
45-minute daysEvery day planned and timed
Short coding levels practice this lesson in CodeGrove, our code lab that runs in the browser. Students write the program, run it and check it, with no account and nothing to install. Use them with the lesson or as practice later.
See the levelsWhat does this lesson cover?
Students often change random lines when an error appears and can't explain what fixed it. This lesson gives them a clear routine: read the ticket, find the error, fix it and test again.
The lab on Day 2 and the activity on Day 3 have online versions that use CodeGrove, our in-browser code lab, in the Bug Tickets level. It practices reading bug tickets and error messages, then fixing programs that ask the user questions. Every online version comes with a paper version, so no internet is needed. CodeGrove is free, with no accounts or sign-ins.
Bug Tickets
Students read three bug tickets and fix each program, on paper or in CodeGrove. They write each exact output and tell how they knew the type of error.
Everything that's included
00 Start Here
- READ FIRST: every file in the lesson and when you use it
- Teacher Guide and Pacing: the plan for each day, what to print and how to grade
- Skills map: which standards each day teaches
01 Present
- One editable PowerPoint deck for all three days, 29 slides, with speaker notes
- Slide script: the speaker notes, printed
- Bell ringers: a short warm-up for each day
02 Student Handouts
- Guided notes: one packet for all three days, in PDF and editable Word. Students fill in the blanks during the slides, with the word bank on the page
- Vocab slip: the lesson's words and what they mean, on one page
03 Labs
- Bug Tickets: students read three bug tickets and fix each program, on paper or in CodeGrove. They write each exact output and tell how they knew the type of error
04 Activities
- A Programmer's Day: students sort a programmer's tasks and name the type of error in six short programs, on paper with computers closed
- Badge Bug: students fix a badge program from a bug ticket and add a comment about the fix, on paper or in CodeGrove. Then they take the lesson quiz
05 Assessment
- Exit tickets: quick questions that show who needs more help
- Lesson quiz: 8 multiple-choice questions and 2 written answers about all three days
06 Answer Keys
- 5 answer key files: a key for each day (its bell ringer, notes and exit ticket) and the activity and lab keys, plus the quiz key
Digital: Google Forms™ + Google Slides™
- 4 Google Forms™ of the exit tickets and the quiz, ready to copy into your Drive
- The multiple choice grades itself, and you grade the written answers
- A Google Slides™ copy of the deck, with the same slides and speaker notes, for Google Classroom™
- Give a Form that asks students to read code only on school-managed Chromebooks in locked mode, and use the paper version on other devices
Online: CodeGrove
- CodeGrove, Bug Tickets level: the online version of the lab on Day 2 and the activity on Day 3
- Every online version has a paper version, so no internet is needed
- Free to use, with no accounts or sign-ins
Why teachers love this lesson
Bug tickets give repairs a purposeEach ticket describes the problem students need to solve, so they can check their fix against it.
Students explain how they found bugsThey name the error type and explain the clues, then add a comment describing a badge program's repair.
Print and digitalEvery page is a print-ready PDF, and the Google Forms™ and Google Slides™ let you teach the same lesson in Google Classroom™.
Real online activitiesStudents can use CodeGrove, our in-browser code lab, on a computer or tablet, and every online version has a paper version that works with no internet.
A key for every pageEvery day has its own answer key, and every written question has a sample answer and what to look for.
Every day fits a 45-minute classEach day's plan is timed activity by activity against real reading and writing speeds.
What Teachers Say
Be the first to review this
Reviews help me a lot, and they help other teachers pick the right resources for their classes. It takes about a minute.
Leave a reviewQuestions teachers ask
How do I get the files after I buy?
Instant download right after checkout: PowerPoint and Word files you can edit, print-ready PDFs, and links that copy the Google Forms™ and Google Slides™ into your Drive.
Can I buy the whole unit or course instead?
Yes. This lesson is part of the Unit 1 bundle and the complete Intro to Python Programming course. Both cost less than buying the lessons one at a time.
Is this AP Computer Science?
No. It is a full-year, non-AP intro to Python course for grades 9 to 12. For AP, see our AP Computer Science A and AP CSP courses.
What should students know before this lesson?
Students can write short programs with print(), variables and input(). They know that Python runs the lines from top to bottom and that output must match letter for letter.
What formats are the files in?
Every page is a print-ready PDF. The slides are an editable PowerPoint and the guided notes an editable Word file. The exit tickets and the quiz also come as Google Forms™, and the deck as Google Slides™.
Which standards does it cover?
Written for Florida's Foundations of Programming course (9007210). The skills map in the lesson shows which standards each day teaches.