Defect Cascading (also called Defect Leakage / Ripple Effect) occurs when one defect in a software module causes multiple failures or defects in other dependent modules.

In simple words:

One bug triggers many other bugs.

---

📌 Simple Definition (Interview-friendly)

Defect cascading is a situation where a defect in one part of the application leads to failures in other related parts of the system.

---

🧩 Real-Time Example

Example: Login Module

• Root Defect: Incorrect session creation after login

• Impact (Cascading Defects):

  • User gets logged out automatically

  • Dashboard fails to load

  • User profile not accessible

  • Payment page throws error

➡️ Though multiple issues appear, the root cause is one defect.

---

🔗 Another Example

Database Change

• Column size changed from VARCHAR(50) to VARCHAR(20)

• Impacts:

  • User registration fails

  • Profile update fails

  • API returns 500 error

➡️ One backend defect → multiple failures.

---

⚠️ Why Defect Cascading Happens

• Tight coupling between modules

• Poor impact analysis

• Incomplete regression testing

• Lack of integration testing

• Incorrect fixes (fix introduces new bugs)

---

🛠 How to Handle Defect Cascading

🔹 1. Root Cause Analysis (RCA)

• Identify origin defect, not just symptoms

🔹 2. Proper Defect Logging

• Log one primary defect

• Link all related failures as child defects

🔹 3. Regression Testing

• Run full or impact-based regression after fix

🔹 4. Integration Testing

• Test interactions between modules

🔹 5. Code Reviews

• Reduce defect introduction during fixes

---

🆚 Defect Cascading vs Defect Leakage

---

📌 One-Line Interview Answer

Defect cascading is when a single defect in one module causes multiple failures in dependent modules due to interdependencies.

---