Introduction

Most people associate testing with running the software. But some of the most valuable defects are found before the system ever runs. This is the role of static testing.

According to ISTQB, static testing evaluates work products—such as requirements, design documents, and code—without execution. Its main objective is defect prevention, not just defect detection.

---

What Is Static Testing?

Static testing involves examining documents or code to identify defects, ambiguities, inconsistencies, and risks early in the lifecycle.

Unlike dynamic testing, static testing:

• does not require a test environment
• can start as soon as artifacts exist
• focuses on quality of understanding and structure

Typical static testing techniques include:

• reviews
• static analysis

---

Static Testing vs Dynamic Testing

Aspect	Static Testing	Dynamic Testing
Code execution	No	Yes
Timing	Very early	After build
Main goal	Defect prevention	Defect detection
Cost to fix defects	Low	Higher

Both are complementary, not alternatives.

---

1️⃣ Reviews

Purpose

To identify defects in documents or code through human examination.

What Can Be Reviewed

• requirements and user stories
• acceptance criteria
• architecture and design documents
• test cases
• source code

Types of Reviews (ISTQB)

• Informal review – ad-hoc feedback
• Walkthrough – author leads the review
• Technical review – peer review with defined roles
• Inspection – formal, structured, metrics-driven

Example

During a requirements review, testers identify ambiguous acceptance criteria that would later cause multiple interpretations during implementation.

Why Reviews Matter

Many severe defects originate in unclear or incomplete requirements. Reviews stop these defects at the source.

---

2️⃣ Static Analysis

Purpose

To analyze source code using tools, without executing it.

What Static Analysis Detects

• coding standard violations
• security vulnerabilities
• dead code
• memory leaks
• complexity and maintainability issues

Example

A static analysis tool flags a potential null pointer dereference before the code reaches testing or production.

Benefits

• fast and repeatable
• consistent enforcement of rules
• ideal for CI pipelines

---

When Static Testing Is Most Effective

Static testing is especially powerful:

• early in the SDLC
• in complex or regulated systems
• when requirements change frequently
• when quality risks are high

It supports Shift Left and test-first strategies.

---

The Role of QA in Static Testing

Testers are not passive participants. They:

• review requirements for testability
• identify missing scenarios and edge cases
• challenge assumptions
• provide early risk feedback

QA acts as a quality filter, not just a defect reporter.

---

Common Misconceptions

• ❌ “Static testing is just documentation review”
• ❌ “Tools replace human reviews”
• ❌ “Static testing slows development”

In reality, static testing accelerates delivery by reducing rework later.

---

Conclusion

Static testing is one of the most cost-effective quality practices available. By finding defects before execution, teams prevent costly rework, reduce risk, and build quality into the product from the very beginning.