Multiple Choice Questions on Fixing Bugs in Scratch Conditionals

📚 Quick Study Guide

• 🔍 Conditionals (if/else blocks) execute code based on whether a condition is true or false.
• 🐛 Bugs in conditionals often arise from incorrect logical operators (`and`, `or`, `not`), wrong variable comparisons, or missing `else` blocks.
• 💡 Debugging tips: Use the `say` block to check variable values at different points, simplify complex conditionals, and test edge cases.
• 📝 Common errors: Forgetting to update a variable that the condition depends on, or using the wrong operator (e.g., `and` instead of `or`).
• 🎮 Testing: Always test your code with different inputs to ensure it behaves as expected under various conditions.

Practice Quiz

1. Which of the following is a common cause of bugs in Scratch conditionals?
   1. A) Using the correct number of blocks.
   2. B) Incorrect logical operators.
   3. C) Properly indented code.
   4. D) Using comments to explain the code.
2. What is a good debugging technique for conditionals in Scratch?
   1. A) Deleting all the code and starting over.
   2. B) Using the `say` block to check variable values.
   3. C) Ignoring the problem and hoping it goes away.
   4. D) Copying code from another project without understanding it.
3. What happens if you forget an `else` block in a Scratch conditional?
   1. A) The program will crash.
   2. B) The code inside the `if` block will run twice.
   3. C) The code might not handle cases where the condition is false.
   4. D) The Scratch cat will meow.
4. What is the purpose of using the `not` operator in a Scratch conditional?
   1. A) To make the condition always true.
   2. B) To reverse the value of a condition.
   3. C) To make the condition always false.
   4. D) To add two numbers together.
5. If a conditional should execute when a variable is greater than 10 AND less than 20, which operator should you use?
   1. A) `or`
   2. B) `not`
   3. C) `and`
   4. D) `join`
6. What should you do after fixing a bug in a Scratch conditional?
   1. A) Assume it's fixed and move on.
   2. B) Test the code with different inputs to ensure it works correctly.
   3. C) Delete the code.
   4. D) Blame someone else for the bug.
7. Which of the following is an example of an edge case to test when debugging conditionals?
   1. A) Using the same input value every time.
   2. B) Ignoring the problem.
   3. C) Using values at the boundaries of the condition (e.g., exactly 10 or 20).
   4. D) Only testing with positive numbers.