Which of the following should you review using static testing?

Question

Options

• AMemory leak during execution
• BPerformance of a module under load
• CInteractive output from a debugger
• DTest plan

• A
  6% (1)
• D
  94% (17)

Explanation

Test plans are documents - they can be read, inspected, and reviewed without running any code, which is the defining characteristic of static testing. Static testing examines work products (requirements, designs, code, test plans) for defects through review techniques rather than execution.

Why the distractors are wrong:

• A (Memory leak during execution) - "during execution" is the giveaway; detecting runtime memory issues requires the program to actually run, making this dynamic testing.
• B (Performance under load) - load/performance testing inherently requires executing the software against simulated or real workloads - purely dynamic.
• C (Debugger output) - a debugger operates on a running process; any output it produces comes from live execution, not from inspecting a static artifact.

Memory tip: If the activity requires running something, it's dynamic. Static testing only ever touches artifacts you can read - documents, source code (unexecuted), models, and plans. Ask yourself: "Can I find this defect without pressing Play?" If yes, it's static.

No community discussion yet for this question.