Skip to main content

Understanding Mistakes in Software Development: Errors, Defects, and Bugs

 

Every software team uses the words “error,” “defect,” and “bug,” often interchangeably. But there’s real power in knowing exactly what each term means—and when it applies

 

1. Mistakes by Phase

Phase What You Find What It’s Called
Requirements & Design A mistake in the design or plan that doesn’t meet what stakeholders want. Defect
Coding A coding or logic mistake in source code Error
Testing & Execution An observable malfunction occurring during software execution or testing. Bug 🐞


1.1 Defect

A defect is any flaw or mismatch in your requirements or design artifacts. It exists before any code runs.

Example: You document “Users must enter a 4-digit PIN,” but stakeholders actually needed 6 digits. That spec mismatch is a defect.


1.2 Error

An error is a mistake made while coding—a typo, wrong operator, missing null check, etc.

Example: In Java you write if (userInput = null) instead of if (userInput == null). That is a compile-time error by the developer.


1.3 Bug 

A bug is the visible failure you see when running or testing the application—what your testers log.

Example: Clicking “Submit” on a form does nothing. The UI doesn’t respond. That runtime symptom is a bug.

 

2. A Real-World Example: Online Checkout

Imagine you’re building an e-commerce checkout:

  1. Requirements Phase (Defect)
    • You write: “Order quantity must be ≤ 0.”
    • Stakeholder actually wants “Order quantity must be > 0.”
    • Result: a defect in your requirements document.
  2. Design Phase (Defect)
    • Your UML diagram routes payment data through the reporting class instead of the payment gateway class.
    • That misplacement is a design defect.
  3. Coding Phase (Error)
    • In your PaymentProcessor class you type:
    • if (amount = 0) {  // assignment instead of comparison
    •     throw new InvalidAmountException();
    • }
    • Java will flag a compile error, but if you fixed the syntax and logic still flips 0 vs. non-zero, that’s an error you introduced.
  4. Testing Phase (Bug)
    • When QA runs the “Buy Now” test, the payment screen never appears.
    • They log: “Checkout button does nothing.” That’s the bug.

 

3. Why “All Bugs Are Defects, But Not All Defects Are Bugs”

  • Defects live in artifacts (requirements, design, code).
  • A bug is a defect that actually manifests as a failure at runtime or during a test case.
  • You can have plenty of defects in a spec or design that never surface as bugs (e.g., a typo in a rarely used help page).

In set-theory terms:

Defects ⊇ Bugs

Every bug traces back to a defect, but many defects never become bugs.

 

4. Next Steps & Best Practices

  • Shift-Left Testing: Catch defects earlier via peer reviews and automated spec checks.
  • Root Cause Analysis: Link every bug back to its originating defect (and human error).
  • Metrics: Track defect density and bug escape rate to measure quality.
  • Tools: Use JIRA or Azure DevOps to tag issues as “Defect (Design)” vs. “Bug (Test).”

Follow on LinkedIn
Labels:

Comments

Post a Comment

Popular posts from this blog

What Is a Feature Flag?

  A feature flag (also known as a feature toggle) is a powerful software development technique that allows developers to enable or disable specific functionality in an application without changing the code or redeploying the software. 🧠 Core Concept Feature flags act like switches embedded in your codebase. They control whether a feature is active or inactive at runtime. This lets teams test, release, or hide features dynamically. 🚀 Benefits Safe Deployments : Deploy code with features turned off, then activate them when ready. A/B Testing : Roll out features to a subset of users to gather feedback. Quick Rollbacks : If something breaks, just flip the flag off—no need to revert code. Continuous Delivery : Decouple feature releases from code deployments for smoother CI/CD pipelines. User Segmentation : Tailor experiences for different user groups. 🧩 Types of Feature Flags Type...
2 comments
Read more

Test Data Design Techniques with Examples

  ✅ 1. Equivalence Partitioning (EP) What it is: Divides input data into partitions of equivalent data from which test cases can be derived. The idea is that if one value in a partition works, all others will too. Example: If a form accepts ages from 18 to 60: Valid partitions: 18–60 Invalid partitions: <18 and >60 Test cases: One value from each partition: 25 (valid), 17 (invalid), 61 (invalid) When to use: When input data can be grouped into ranges or categories. ✅ 2. Boundary Value Analysis (BVA) What it is: Focuses on values at the edges (boundaries) of input ranges, where defects are most likely to occur. Example: For an input field that accepts values from 1 to 100: Test boundaries: 0, 1, 2 and 99, 100, 101 Test cases: 0 (just below), 1 (lower boundary), 2 (just above) 99 (just below), 100 (upper boundary), 101 (just above) When to use: When input fields have defined minimum and maximu...
Post a Comment
Read more