Modules
Beginner7 min read

7 Software Testing Principles

sign in to track

The seven principles defined by ISTQB are the philosophical backbone of professional software testing. They guide how testers think about coverage, effort allocation, and the inherent limitations of testing as a discipline.

Key Points

  • 1. Testing shows the presence of bugs, not their absence.
  • 2. Exhaustive testing is impossible — test smarter, not more.
  • 3. Early testing saves cost — a bug found in requirements costs 10× less than in production.
  • 4. Defect clustering — a small number of modules usually contain most defects (Pareto principle).
  • 5. The Pesticide Paradox — repeating the same tests eventually stops finding new bugs; evolve your suite.
  • 6. Testing is context-dependent — a banking app needs far more rigour than a personal blog.
  • 7. Absence-of-errors fallacy — a bug-free product that doesn't meet user needs is still a failure.
Expert Pro Tip

Print these principles and review them when a sprint gets rushed. They are your professional shield when stakeholders push back on test coverage.