What is Static Testing?

Static testing finds defects without executing the code, through reviews of work products (requirements, design, code) and automated static analysis, catching issues earlier and more cheaply than running the software.

Start a Free Mock Interview

Free to start · 7-day trial on paid plans

IN DEPTH

In depth.

Static testing splits into two families. Reviews are human examination of work products: informal reviews, walkthroughs, technical reviews, and formal inspections, applied to requirements, designs, test cases, and code. They catch ambiguous requirements and design flaws before a single line is written, which is the cheapest possible place to fix a defect. Static analysis is tool-driven: linters, type checkers, and SAST scan source code for bugs, style violations, security issues, and complexity without running it.

The contrast is with dynamic testing, which executes the software and observes behavior (unit, integration, system, performance tests). Static testing is a form of verification (are we building it right, against the spec) while much dynamic testing leans toward validation (are we building the right thing). They are complementary: static catches different defects, earlier; dynamic catches runtime and integration behavior static cannot see.

The interview value of static testing is the shift-left argument: a requirements review that removes an ambiguity prevents a whole chain of downstream bugs, far cheaper than catching them in QA or production.

WHY IT MATTERS

Why interviewers ask about this.

Static testing shows you understand that testing starts before code runs. Interviewers value the shift-left mindset, reviews and static analysis catching defects early, and the clear static-versus-dynamic distinction.

EXAMPLE

Example scenario.

A requirements review (static testing) catches that "users can reset their password" never specifies what happens to active sessions. Clarifying it up front prevents a security defect that would otherwise have shipped and been caught, expensively, only after a dynamic test or a production incident.

TIP

Interview tip.

Define static testing as finding defects without running the code (reviews + static analysis) and contrast it with dynamic testing. Tie it to shift-left and to verification vs validation for a strong, structured answer.

FAQ

Frequently asked questions.

What is the difference between static and dynamic testing?

Static testing finds defects without executing the code, through reviews and static analysis. Dynamic testing executes the software and observes its behavior (unit, integration, system, performance). They are complementary and catch different defect types.

Is code review a form of static testing?

Yes. Code review is a review-based static testing technique. So are walkthroughs, technical reviews, and formal inspections of requirements, designs, and test cases, alongside tool-based static analysis.