Testing and Debugging Python Code

Testing and Debugging: Building Bulletproof Applications

Software without tests is like flying without instruments. NASA, Google, and every major tech company require comprehensive tests before deploying code. This chapter teaches you how to find bugs quickly (debugging) and prevent them from happening (testing). You'll master techniques used in production systems at ISRO, TCS, and Infosys.

The Cost of Bugs in Production

A single bug in production can cost millions. In 2012, a bug in trading algorithms caused Knight Capital $440 million loss in 45 minutes. Testing prevents these disasters. Professional developers spend 30-40% of time writing tests because bugs are expensive to fix in production.

Debugging Technique 1: Strategic Print Debugging

Print statements are your first weapon against bugs. Use them strategically to understand program flow:

def calculate_student_gpa(marks):
    """Calculate GPA from marks (real school system)"""
    print(f"[DEBUG] Input marks: {marks}")

    # Convert marks to grade points
    gpa = 0
    for mark in marks:
        print(f"[DEBUG] Processing mark: {mark}")
        if mark >= 90:
            gpa += 4.0
        elif mark >= 80:
            gpa += 3.5
        elif mark >= 70:
            gpa += 3.0
        else:
            gpa += 2.0

    avg_gpa = gpa / len(marks)
    print(f"[DEBUG] Total GPA points: {gpa}, Count: {len(marks)}")
    print(f"[DEBUG] Average GPA: {avg_gpa}")
    return avg_gpa

# Test the function
student_marks = [92, 88, 85, 78]
result = calculate_student_gpa(student_marks)
print(f"Final GPA: {result}")

# Output shows flow:
# [DEBUG] Input marks: [92, 88, 85, 78]
# [DEBUG] Processing mark: 92
# [DEBUG] Processing mark: 88
# ... etc
      

Debugging Technique 2: Using Python Debugger (pdb) - Step Through Code

For complex bugs, use the Python debugger to step through code line by line:

import pdb

def calculate_average_marks_in_school(student_marks_dict):
    """Calculate average marks per student"""
    averages = {}

    for student_id, marks in student_marks_dict.items():
        pdb.set_trace()  # Execution pauses here
        # Now you can inspect variables, step through lines, etc.

        total = sum(marks)
        average = total / len(marks)
        averages[student_id] = average

    return averages

# Call with test data
data = {
    'student_101': [92, 88, 85],
    'student_102': [78, 82, 79]
}

result = calculate_average_marks_in_school(data)

# pdb commands when paused:
# n - next line
# s - step into function
# c - continue execution
# p variable_name - print variable
# l - list code
# h - help
      

Debugging Technique 3: Assertions - Catch Wrong Assumptions Early

Assertions validate that assumptions are correct. They fail loudly if something's wrong:

def transfer_money_upi(sender_balance, amount):
    """Simulate UPI transfer (real payment system logic)"""

    # Validate assumptions
    assert sender_balance >= 0, "Balance cannot be negative"
    assert amount > 0, "Amount must be positive"
    assert isinstance(amount, (int, float)), "Amount must be number"

    # Check sufficient balance
    assert sender_balance >= amount, f"Insufficient balance: {sender_balance}"

    # Process transfer
    new_balance = sender_balance - amount
    return new_balance

# Test cases
try:
    # Valid transfer
    balance = transfer_money_upi(1000, 500)
    print(f"Success: new balance {balance}")

    # This will fail with assertion error
    transfer_money_upi(100, 500)  # Insufficient balance
except AssertionError as e:
    print(f"Assertion failed: {e}")
      

Comprehensive Unit Testing with unittest Framework

Write systematic tests for each function. This is how professional code is built:

import unittest

class GradingSystem:
    """Calculate grades for students"""

    @staticmethod
    def get_grade(percentage):
        """Return grade based on percentage"""
        if percentage >= 90:
            return 'A+'
        elif percentage >= 80:
            return 'A'
        elif percentage >= 70:
            return 'B'
        elif percentage >= 60:
            return 'C'
        else:
            return 'F'

    @staticmethod
    def calculate_percentage(marks, total_marks=100):
        """Calculate percentage"""
        if total_marks == 0:
            raise ValueError("Total marks cannot be zero")
        return (marks / total_marks) * 100

class TestGradingSystem(unittest.TestCase):
    """Test suite for grading system"""

    def setUp(self):
        """Run before each test"""
        self.grader = GradingSystem()

    def test_grade_a_plus(self):
        """Test A+ grade (90+)"""
        self.assertEqual(self.grader.get_grade(95), 'A+')
        self.assertEqual(self.grader.get_grade(90), 'A+')

    def test_grade_a(self):
        """Test A grade (80-89)"""
        self.assertEqual(self.grader.get_grade(85), 'A')
        self.assertEqual(self.grader.get_grade(80), 'A')

    def test_grade_b(self):
        """Test B grade (70-79)"""
        self.assertEqual(self.grader.get_grade(75), 'B')

    def test_grade_c(self):
        """Test C grade (60-69)"""
        self.assertEqual(self.grader.get_grade(65), 'C')

    def test_grade_f(self):
        """Test F grade (below 60)"""
        self.assertEqual(self.grader.get_grade(50), 'F')
        self.assertEqual(self.grader.get_grade(0), 'F')

    def test_percentage_calculation(self):
        """Test percentage calculation"""
        percentage = self.grader.calculate_percentage(85, 100)
        self.assertEqual(percentage, 85.0)

        percentage = self.grader.calculate_percentage(50, 100)
        self.assertEqual(percentage, 50.0)

    def test_edge_cases(self):
        """Test boundary conditions"""
        # Exactly at boundary
        self.assertEqual(self.grader.get_grade(89.9), 'A')
        self.assertEqual(self.grader.get_grade(90.0), 'A+')

    def test_invalid_total_marks(self):
        """Test division by zero protection"""
        with self.assertRaises(ValueError):
            self.grader.calculate_percentage(85, 0)

if __name__ == '__main__':
    # Run tests
    unittest.main(verbosity=2)

# Output:
# test_edge_cases (__main__.TestGradingSystem) ... ok
# test_grade_a (__main__.TestGradingSystem) ... ok
# ... all tests passing
      

Test-Driven Development (TDD): Write Tests First, Code Second

Professional development follows TDD: write test first, then implement code to pass it. This ensures clean design:

import unittest

# Step 1: Write test FIRST (before implementation)
class TestUPIValidator(unittest.TestCase):
    def test_valid_upi(self):
        """Test valid UPI ID"""
        self.assertTrue(validate_upi("student@upi"))
        self.assertTrue(validate_upi("rahul.sharma@okaxis"))

    def test_invalid_upi_no_at_symbol(self):
        """Test UPI without @ symbol"""
        self.assertFalse(validate_upi("studentupi"))

    def test_invalid_upi_no_bank(self):
        """Test UPI with @ but no bank"""
        self.assertFalse(validate_upi("student@"))

    def test_upi_case_insensitive(self):
        """Test uppercase/lowercase handling"""
        self.assertTrue(validate_upi("STUDENT@UPI"))
        self.assertTrue(validate_upi("Student@Upi"))

# Step 2: Write code to pass tests
def validate_upi(upi):
    """Validate UPI format"""
    if not isinstance(upi, str):
        return False

    upi = upi.lower()

    if '@' not in upi:
        return False

    parts = upi.split('@')
    if len(parts) != 2:
        return False

    username, bank = parts
    if not username or not bank:
        return False

    return True

if __name__ == '__main__':
    unittest.main(verbosity=2)
      

Real-World Example: Testing E-Commerce Payment System (Zomato Scale)

import unittest
from datetime import datetime

class PaymentProcessor:
    def __init__(self):
        self.transactions = []

    def process_payment(self, amount, payment_method, user_id):
        """Process payment and track transaction"""

        # Validation
        if amount <= 0:
            raise ValueError("Amount must be positive")

        if payment_method not in ['upi', 'card', 'wallet']:
            raise ValueError("Invalid payment method")

        # Simulate payment
        transaction = {
            'user_id': user_id,
            'amount': amount,
            'method': payment_method,
            'timestamp': datetime.now(),
            'status': 'success'
        }

        self.transactions.append(transaction)
        return transaction

class TestPaymentProcessor(unittest.TestCase):
    def setUp(self):
        self.processor = PaymentProcessor()

    def test_valid_payment_upi(self):
        """Test valid UPI payment"""
        result = self.processor.process_payment(500, 'upi', 'user_101')
        self.assertEqual(result['amount'], 500)
        self.assertEqual(result['method'], 'upi')
        self.assertEqual(result['status'], 'success')

    def test_valid_payment_card(self):
        """Test valid card payment"""
        result = self.processor.process_payment(1000, 'card', 'user_102')
        self.assertEqual(result['amount'], 1000)
        self.assertEqual(result['method'], 'card')

    def test_zero_amount_fails(self):
        """Test zero amount rejection"""
        with self.assertRaises(ValueError):
            self.processor.process_payment(0, 'upi', 'user_101')

    def test_negative_amount_fails(self):
        """Test negative amount rejection"""
        with self.assertRaises(ValueError):
            self.processor.process_payment(-100, 'upi', 'user_101')

    def test_invalid_payment_method(self):
        """Test invalid payment method"""
        with self.assertRaises(ValueError):
            self.processor.process_payment(500, 'bitcoin', 'user_101')

    def test_transaction_logged(self):
        """Test transaction is recorded"""
        initial_count = len(self.processor.transactions)
        self.processor.process_payment(250, 'wallet', 'user_103')
        self.assertEqual(len(self.processor.transactions), initial_count + 1)

if __name__ == '__main__':
    unittest.main(verbosity=2)
      

Testing Checklist for Professional Code

• Test normal/happy path (inputs that should work)
• Test edge cases (0, negative, very large values, empty data)
• Test invalid inputs (wrong types, out of range)
• Test error handling (exceptions caught properly)
• Test side effects (file created, database updated)
• Aim for 80%+ code coverage (% of code tested)
• Make tests independent (one test's failure doesn't affect others)
• Use descriptive test names (test_transfer_insufficient_balance is better than test_1)

Debugging Best Practices

• Reproduce the bug reliably first (if you can't reproduce, you can't fix)
• Use print debugging for simple cases, pdb for complex ones
• Test a hypothesis: "I think the bug is in function X"—use debugger to verify
• Isolate the problem: disable code sections to find exact line causing bug
• Write a test that fails with the bug, passes when fixed
• Don't guess—use debugger to see actual values

Key Takeaways

• Testing is not optional—it's how professional code is written
• Unit tests catch bugs early, saving hours of debugging later
• Test-Driven Development (TDD) produces cleaner, simpler code
• Print debugging is quick but pdb is powerful for complex bugs
• Assertions validate assumptions—fail fast if something's wrong
• All major companies (Google, Amazon, ISRO) require >80% code coverage

Practice Problems

1. Write unit tests for a calculator with add, subtract, multiply, divide functions
2. Create a test suite for a function that validates email addresses
3. Debug a buggy function using pdb (set breakpoints, inspect variables)
4. Write tests for a function before implementing it (TDD practice)
5. Create tests for a UPI payment validator with valid/invalid cases
6. Test a grade calculation function with boundary cases (89.9 vs 90.0)
7. Write tests for a data processing function that handles missing values

Under the Hood: Testing and Debugging Python Code

Here is what separates someone who merely USES technology from someone who UNDERSTANDS it: knowing what happens behind the screen. When you tap "Send" on a WhatsApp message, do you know what journey that message takes? When you search something on Google, do you know how it finds the answer among billions of web pages in less than a second? When UPI processes a payment, what makes sure the money goes to the right person?

Understanding Testing and Debugging Python Code gives you the ability to answer these questions. More importantly, it gives you the foundation to BUILD things, not just use things other people built. India's tech industry employs over 5 million people, and companies like Infosys, TCS, Wipro, and thousands of startups are all built on the concepts we are about to explore.

This is not just theory for exams. This is how the real world works. Let us get into it.

Object-Oriented Programming: Modelling the Real World

OOP lets you model real-world entities as code "objects." Each object has properties (data) and methods (behaviour). Here is a practical example:

class BankAccount:
    """A simple bank account — like what SBI or HDFC uses internally"""

    def __init__(self, holder_name, initial_balance=0):
        self.holder = holder_name
        self.balance = initial_balance    # Private in practice
        self.transactions = []            # History log

    def deposit(self, amount):
        if amount <= 0:
            raise ValueError("Deposit must be positive")
        self.balance += amount
        self.transactions.append(f"+₹{amount}")
        return self.balance

    def withdraw(self, amount):
        if amount > self.balance:
            raise ValueError("Insufficient funds!")
        self.balance -= amount
        self.transactions.append(f"-₹{amount}")
        return self.balance

    def statement(self):
        print(f"
--- Account Statement: {self.holder} ---")
        for t in self.transactions:
            print(f"  {t}")
        print(f"  Balance: ₹{self.balance}")

# Usage
acc = BankAccount("Rahul Sharma", 5000)
acc.deposit(15000)      # Salary credited
acc.withdraw(2000)      # UPI payment to Swiggy
acc.withdraw(500)       # Metro card recharge
acc.statement()

This is encapsulation — bundling data and behaviour together. The user of BankAccount does not need to know HOW deposit works internally; they just call it. Inheritance lets you extend this: a SavingsAccount could inherit from BankAccount and add interest calculation. Polymorphism means different account types can respond to the same .withdraw() method differently (savings accounts might check minimum balance, current accounts might allow overdraft).

Real-World System Design: Swiggy's Architecture

When you order food on Swiggy, here is what happens behind the scenes in about 2 seconds: your location is geocoded (algorithms), nearby restaurants are queried from a spatial index (data structures), menu prices are pulled from a database (SQL), delivery time is estimated using ML models trained on historical data (AI), the order is placed in a distributed message queue (Kafka), a delivery partner is assigned using a matching algorithm (optimization), and real-time tracking begins using WebSocket connections (networking). EVERY concept in your CS curriculum is being used simultaneously to deliver your biryani.

How the Web Request Cycle Works

Every time you visit a website, a precise sequence of events occurs. Here is the flow:

    You (Browser)          DNS Server          Web Server
        |                      |                    |
        |---[1] bharath.ai --->|                    |
        |                      |                    |
        |<--[2] IP: 76.76.21.9|                    |
        |                      |                    |
        |---[3] GET /index.html ----------------->  |
        |                      |                    |
        |                      |    [4] Server finds file,
        |                      |        runs server code,
        |                      |        prepares response
        |                      |                    |
        |<---[5] HTTP 200 OK + HTML + CSS + JS --- |
        |                      |                    |
   [6] Browser parses HTML                          |
       Loads CSS (styling)                          |
       Executes JS (interactivity)                  |
       Renders final page                           |

Step 1-2 is DNS resolution — converting a human-readable domain name to a machine-readable IP address. Step 3 is the HTTP request. Step 4 is server-side processing (this is where frameworks like Node.js, Django, or Flask operate). Step 5 is the HTTP response. Step 6 is client-side rendering (this is where React, Angular, or Vue operate).

In a real-world scenario, this cycle also involves CDNs (Content Delivery Networks), load balancers, caching layers, and potentially microservices. Indian companies like Jio use this exact architecture to serve 400+ million subscribers.

Production Engineering: Testing and Debugging Python Code at Scale

Understanding testing and debugging python code at an academic level is necessary but not sufficient. Let us examine how these concepts manifest in production environments where failure has real consequences.

Consider India's UPI system processing 10+ billion transactions monthly. The architecture must guarantee: atomicity (a transfer either completes fully or not at all — no half-transfers), consistency (balances always add up correctly across all banks), isolation (concurrent transactions on the same account do not interfere), and durability (once confirmed, a transaction survives any failure). These are the ACID properties, and violating any one of them in a payment system would cause financial chaos for millions of people.

At scale, you also face the thundering herd problem: what happens when a million users check their exam results at the same time? (CBSE result day, anyone?) Without rate limiting, connection pooling, caching, and graceful degradation, the system crashes. Good engineering means designing for the worst case while optimising for the common case. Companies like NPCI (the organisation behind UPI) invest heavily in load testing — simulating peak traffic to identify bottlenecks before they affect real users.

Monitoring and observability become critical at scale. You need metrics (how many requests per second? what is the 99th percentile latency?), logs (what happened when something went wrong?), and traces (how did a single request flow through 15 different microservices?). Tools like Prometheus, Grafana, ELK Stack, and Jaeger are standard in Indian tech companies. When Hotstar streams IPL to 50 million concurrent users, their engineering team watches these dashboards in real-time, ready to intervene if any metric goes anomalous.

The career implications are clear: engineers who understand both the theory (from chapters like this one) AND the practice (from building real systems) command the highest salaries and most interesting roles. India's top engineering talent earns ₹50-100+ LPA at companies like Google, Microsoft, and Goldman Sachs, or builds their own startups. The foundation starts here.

Key Vocabulary

Here are important terms from this chapter that you should know:

💡 Interview-Style Problem

Here is a problem that frequently appears in technical interviews at companies like Google, Amazon, and Flipkart: "Design a URL shortener like bit.ly. How would you generate unique short codes? How would you handle millions of redirects per second? What database would you use and why? How would you track click analytics?"

Think about: hash functions for generating short codes, read-heavy workload (99% redirects, 1% creates) suggesting caching, database choice (Redis for cache, PostgreSQL for persistence), and horizontal scaling with consistent hashing. Try sketching the system architecture on paper before looking up solutions. The ability to think through system design problems is the single most valuable skill for senior engineering roles.

Where This Takes You

The knowledge you have gained about testing and debugging python code is directly applicable to: competitive programming (Codeforces, CodeChef — India has the 2nd largest competitive programming community globally), open-source contribution (India is the 2nd largest contributor on GitHub), placement preparation (these concepts form 60% of technical interview questions), and building real products (every startup needs engineers who understand these fundamentals).

India's tech ecosystem offers incredible opportunities. Freshers at top companies earn ₹15-50 LPA; experienced engineers at FAANG companies in India earn ₹50-1 Cr+. But more importantly, the problems being solved in India — digital payments for 1.4 billion people, healthcare AI for rural areas, agricultural tech for 150 million farmers — are some of the most impactful engineering challenges in the world. The fundamentals you are building will be the tools you use to tackle them.

Crafted for Class 8–9 • Projects & Applied • Aligned with NEP 2020 & CBSE Curriculum