BBP Python Debugging Challenge

🎮 Activity Time! 🔍 Detective Mode Activated!

⏰ Time Estimate: 45-60 minutes
🎯 What You'll Master:

• Become a code detective who finds and fixes bugs! 🕵️‍♂️
• Debug 5 challenging puzzles that test your Python skills
• Master conditionals, user input, lists, and random selection
• Build your confidence in spotting and solving code problems

Activity Instruction:

Welcome, young detective! 🔍 In this special debugging challenge, you'll put on your detective hat and solve coding mysteries. Each challenge is a puzzle waiting to be solved. Remember: Every bug you find makes you a stronger coder! Mistakes are just stepping stones to success - even the best programmers debug code every day!

📋 Before You Start:

• Have your detective notebook ready (paper or digital notes)
• Remember: Bugs are puzzles, not problems!
• Take deep breaths - debugging requires patience
• Save your work frequently - detectives keep good records!

Setup Instructions

1. Open EduBlocks - Go to https://app.edublocks.org/login and sign in with your Google account
2. Start New Projects - Click the "Editor" icon for each new challenge
3. Resume Projects - Click the "Projects" icon to continue your work

🚀 Setup Steps:

1. Select Mode -> Choose Python 3 mode
2. Name Your Project -> Use clear names like "Debugging Challenge 1"
3. Start Coding -> Click "Start Coding" button
4. Save Immediately -> Click "Save" at the top-right (and save every few minutes!)

💡 Detective Tip!

Create a separate project for each challenge. This makes it easier to submit your work and keeps your detective case files organized! 🗂️

🔍 Debugging Challenge One: The Dessert Detective

Your Mission:

Create a guessing game where users try to guess your favorite dessert! 🍰

📝 Steps to Solve This Mystery:

1. Analyze the Evidence - Look at the example outputs below
2. Plan Your Solution - Think about what blocks you'll need
3. Build Your Program - Create the guessing game step by step
4. Test Your Code - Make sure both correct and incorrect guesses work!

🎯 Program Requirements:

1. Ask the user to guess your favorite dessert
2. Check if their guess matches your favorite
3. Show a happy message for correct guesses ✅
4. Show an encouraging message for wrong guesses ❌

💡 Detective Clue #1

Think about what you need:

• A variable to store YOUR favorite dessert
• An input block to get the user's guess
• An if/else statement to check the answer Don't forget to make your messages friendly! 😊

Evidence File A: Correct Guess

Evidence File B: Wrong Guess

🔍 Debugging Challenge 2: The Random Dessert Mystery

Your Mission:

Create a program that randomly picks one of YOUR favorite desserts and asks if the user likes it too! 🍨

📝 Steps to Crack This Case:

1. Create Your Evidence List - Make a list of your favorite desserts
2. Add Some Randomness - Use the random module to pick one dessert
3. Question the Suspect - Ask if they like that dessert (yes/no)
4. React Appropriately - Give different responses based on their answer

🎯 Program Requirements:

1. Store multiple favorite desserts in a list
2. Randomly select one dessert from your list
3. Ask the user if they also like that dessert (yes/no question)
4. If yes -> Show excitement! "Wow, we have the same taste!" 🎉
5. If no -> Encourage them to try it! "You should give it a try!" 🤔

💡 Detective Clue #2

Building blocks you'll need:

• A list to store multiple desserts
• The random.choice() function
• An input block for yes/no response
• An if/else statement for different reactions Remember: Make your responses sound natural and friendly!

Evidence File A: User Says Yes

Evidence File B: User Says No

🔍 Debugging Challenge 3: The Case of the Broken Blocks

Your Mission:

A fellow coder needs your help! Their code has bugs and won't run properly. Can you spot what's wrong? 🐛

📝 Detective Investigation Steps:

1. Examine the Evidence - Study the broken code carefully
2. Identify the Suspects - Look for syntax errors or logic problems
3. Test Your Theory - Fix the bugs one by one
4. Verify Success - Make sure your output matches the expected result

💡 Detective Clue #3

Common bug hideouts to check:

• Missing quotation marks or parentheses
• Wrong variable names
• Incorrect indentation
• Logic that doesn't make sense Take your time - good detectives are thorough! 🔍

The Broken Code:

Your Target Output:

⚠️ Detective Warning: Don't just copy the answer! Understanding WHY the bug happened will make you a better coder!

🔍 Debugging Challenge 4: The Mathematical Mystery

Your Mission:

A calculator program is broken! It should add two numbers, but something's not working right. Time to investigate! 🧮

📝 Debug Investigation Process:

1. Study the Crime Scene - Look at the buggy code blocks
2. Interview the Variables - Are inputs being handled correctly?
3. Check the Math Department - Is the calculation working properly?
4. Test Your Fix - Run the program with different numbers

🎯 The Program Should:

• Ask for two numbers from the user
• Add them together correctly
• Display the result clearly

💡 Detective Clue #4

Math bugs often hide in:

• Input conversion (strings vs numbers)
• Variable naming mistakes
• Calculation order
• Output formatting Remember: Computers need exact instructions! 🤖

The Suspicious Code:

Expected Behavior When Fixed:

💡 Pro Detective Move: Test with easy numbers first (like 5 + 5) to make sure it's working!

🔍 Debugging Challenge 5: The Final Case

Your Mission:

This is your toughest case yet! The program has multiple bugs involving variables and output. Can you solve them all? 🎯

📝 Master Detective Steps:

1. Map the Variables - Track each variable from start to finish
2. Follow the Data Flow - How does information move through the program?
3. Check the Output Format - Is everything displaying correctly?
4. Run Multiple Tests - Try different inputs to ensure it always works

💡 Detective Clue #5

Advanced bug patterns to watch for:

• Variables used before they're defined
• Wrong variable names in different parts
• Missing spaces or formatting in output
• Type mismatches (text vs numbers) You're almost a debugging master! 🏆

The Complex Case:

Your Success Target:

🌟 Detective Achievement: If you solve this one, you've proven you can debug like a pro!

🛠️ Troubleshooting Tips

If you're stuck, try these detective techniques:

1. Read Error Messages Carefully - They often tell you exactly where the bug is hiding!
2. Test One Thing at a Time - Fix one bug before moving to the next
3. Use Print Statements - Add print blocks to see what your variables contain
4. Take a Break - Sometimes fresh eyes spot bugs better!
5. Ask for Clues - It's okay to ask a friend or teacher for hints (not answers!)

🏆 Challenge Yourself!

Ready for some extra detective work? Try these bonus challenges:

• Speed Detective: Time yourself solving each challenge - can you get faster?
• Bug Creator: After fixing bugs, create your own buggy program for a friend to debug!
• Code Reviewer: Explain to someone else WHY each bug was wrong
• Pattern Finder: What types of bugs appear most often? Make a "Bug Pattern Guide"!

🎉 Congratulations, Code Detective!

You've completed all 5 debugging challenges! 🕵️‍♂️✨

What You've Accomplished:

• ✅ Found and fixed syntax errors
• ✅ Solved logic problems
• ✅ Debugged input/output issues
• ✅ Fixed calculation errors
• ✅ Became a debugging champion!

Remember: Every programmer is also a debugger! The skills you've learned today will help you for your entire coding journey. Bugs aren't enemies - they're puzzles that make you smarter! 🧩

📤 Project Submission

You've solved all the cases! Now it's time to submit your detective work:

🎯 Submit Your 5 Debugging Projects Here

📋 Submission Checklist:

• All 5 challenges completed
• Each program tested and working
• 5 separate project links ready
• Double-checked all solutions

Note: You need to submit 5 project links for this activity - one for each debugging challenge.

🌟 You're now an official Code Detective! Keep those debugging skills sharp! 🌟