Static testing and reviews

Question 1

What is a static review

Answer 1

In contrast to dynamic testing, which requires the execution of the software being tested, static testing
relies on the manual examination of work products (i.e., reviews) or tool-driven evaluation of the code or
other work products (i.e., static analysis). Both types of static testing assess the code or other work
product being tested without actually executing the code or work product being tested.

Question 2

What work products can be statically reviewed?

Answer 2

Almost any work product can be examined using static testing (such as manual reviews or tools based static analysis).

Examples include: code, web pages, Epics, user stories, acceptance criteria, testware, user guides, contracts, schedules, etc.

Question 3

What are the benefits of static testing

Answer 3

• Applied early can cheaply and efficiently detect/corrects defects prior to dynamic test execution.
• Can detect defects which aren’t easily detected by dynamic testing.
• Prevents defects in design/coding by uncovering inconsistencies, ambiguities, contradictions,
  omissions, etc.
• Increasing development productivity (e.g., due to improved design, more maintainable code).
• Reducing development/testing cost and time.
  -Improving communication between team members in the course of participating in reviews

Question 4

Why is static testing more likely to find defects in work products directly?

Answer 4

Because defects can be found directly in the code rather then being found as failures after the code has run in dynamic testing.