Defensive Programming and Error Handling

Active learning works because defensive programming requires students to engage with real crashes, not just theory. Hands-on debugging and scenario testing make abstract concepts like exception handling concrete and memorable.

• JC 1
• Computing
• 4 activities
• 25 min–45 min

Learning Objectives

1. Analyze the potential failure points in a given Python program by identifying inputs that could cause exceptions.
2. Evaluate the effectiveness of different error handling strategies (e.g., logging, user feedback, default values) in preventing program crashes.
3. Create a Python program that robustly handles common exceptions like `ValueError` and `TypeError` using try-except blocks.
4. Compare the outcomes of running code with and without defensive programming techniques when presented with invalid inputs.

Escape Room

⏱ 30 min·Pairs

Pair Debug: Faulty Calculator Challenge

Pairs receive a basic calculator function with division by zero and invalid inputs. They run test cases, identify crashes, then implement try-except blocks with user-friendly messages. Pairs swap code for peer testing and refinement.

Prepare & details

Why is it impossible to prove that a program is 100 percent free of bugs?

Facilitation Tip: During Pair Debug, circulate and ask each pair to explain why their try-except block covers the most common input errors in their calculator.

Setup: Group tables with puzzle envelopes, optional locked boxes

Materials: Puzzle packets (4-6 per group), Lock boxes or code sheets, Timer (projected), Hint cards

• Remember
• Apply
• Analyze
• Relationship Skills
• Self-Management

Escape Room

⏱ 45 min·Small Groups

Small Group: Input Invasion Stations

Set up stations with code snippets vulnerable to string inputs, empty lists, or None values. Groups rotate, add validation and try-except at each, then demo one fix to the class. Record successes and failures in a shared log.

Prepare & details

How does a programmer balance the need for user convenience with the need for strict data validation?

Facilitation Tip: For Input Invasion Stations, assign each small group a different invalid input type to test, ensuring all scenarios are covered in one rotation.

Setup: Group tables with puzzle envelopes, optional locked boxes

Materials: Puzzle packets (4-6 per group), Lock boxes or code sheets, Timer (projected), Hint cards

• Remember
• Apply
• Analyze
• Relationship Skills
• Self-Management

Escape Room

⏱ 35 min·Whole Class

Whole Class: Error Scenario Simulation

Project a function and distribute input cards with normal, edge, and malicious cases. Class votes on predictions, runs code live, discusses crashes, then votes on collective try-except solutions. Update code iteratively based on input.

Prepare & details

What is the difference between testing for correctness and testing for robustness?

Facilitation Tip: In Error Scenario Simulation, have students act out both the user and the program to physically demonstrate graceful recovery.

Setup: Group tables with puzzle envelopes, optional locked boxes

Materials: Puzzle packets (4-6 per group), Lock boxes or code sheets, Timer (projected), Hint cards

• Remember
• Apply
• Analyze
• Relationship Skills
• Self-Management

Escape Room

⏱ 25 min·Individual

Individual: Personal Code Audit

Students audit their prior unit project for error risks, add try-except and validations, then test with 10 self-generated inputs. Submit before-after code with a reflection on changes made.

Prepare & details

Why is it impossible to prove that a program is 100 percent free of bugs?

Facilitation Tip: For Personal Code Audit, provide a checklist of common exceptions to guide students as they review their own code.

Setup: Group tables with puzzle envelopes, optional locked boxes

Materials: Puzzle packets (4-6 per group), Lock boxes or code sheets, Timer (projected), Hint cards

• Remember
• Apply
• Analyze
• Relationship Skills
• Self-Management

Teaching This Topic

Experienced teachers approach this topic by focusing on observable crashes and recovery. They avoid overemphasizing perfect code and instead model how to prioritize handling the errors that actually occur. Research shows that students learn better when they see try-except as a safety net, not a flaw in their logic. Teachers should also explicitly link syntax errors to runtime errors by showing how one leads to the other during execution.

What to Expect

Successful learning looks like students confidently identifying where code may fail and writing precise try-except blocks to handle those failures. They should explain why robustness matters and critique code that relies on perfect input.

Watch Out for These Misconceptions

Common Misconception

During Pair Debug, students may assume their calculator will never crash if they test it with obvious inputs.

What to Teach Instead

During Pair Debug, guide students to intentionally test edge cases like empty strings, negative numbers, or symbols to prove that no input set can eliminate all crashes.

Common Misconception

During Input Invasion Stations, students might claim try-except blocks make programs noticeably slower.

What to Teach Instead

During Input Invasion Stations, have groups benchmark crashing vs handled code with loops of 1,000 invalid inputs to demonstrate that handling adds negligible overhead.

Common Misconception

During Error Scenario Simulation, students confuse syntax errors with runtime errors.

What to Teach Instead

During Error Scenario Simulation, have students first trigger a syntax error by running code with a typo, then fix it and trigger a runtime error with invalid input to clearly separate the two types.

Assessment Ideas

Exit Ticket

After Faulty Calculator Challenge, provide a short Python snippet with a ValueError risk. Ask students to write a try-except block and explain what happens during the error.

Discussion Prompt

After Input Invasion Stations, present the file upload scenario and ask students to share two exceptions they identified and their handling strategies in a whole-class discussion.

Peer Assessment

During Personal Code Audit, have students test each other’s functions with three invalid inputs and provide feedback on crash behavior and error handling improvements.

Extensions & Scaffolding

• Challenge: Ask students to extend their calculator to handle division by zero and explain how their try-except now covers two distinct errors.
• Scaffolding: Provide a partially completed try-except block with placeholders for the exception type and error message to help struggling students focus on logic.
• Deeper exploration: Have students research how Python’s logging module can be used to record errors without crashing, then implement it in their code.

Key Vocabulary

Exception	An event that occurs during program execution that disrupts the normal flow of instructions, often indicating an error.
Try-Except Block	A Python construct used to handle exceptions; the code that might raise an exception is placed in the 'try' block, and the code to execute if an exception occurs is in the 'except' block.
Robustness	The ability of a program to continue operating correctly even when faced with unexpected inputs or conditions, rather than crashing.
Graceful Error Handling	The practice of managing errors in a way that minimizes disruption to the user and the program, often by providing informative messages or alternative actions.