Chapter 3: Static Testing

Question 1

software under test does not need to be executed

Answer 1

static testing

Code, process specification, system architecture specification or other work products are evaluated through manual examination (e.g., reviews)

Question 2

Static testing can be applied for both verification and validation

Question 3

Almost any work product can be examined using static testing.

Answer 3

Examples include requirement specification documents, source code, test plans, test cases, product backlog items, test charters, project
documentation, contracts and models.

Question 4

Differences between Static Testing and Dynamic Testing

Answer 4

Static testing finds defects directly, while dynamic testing causes failures from which the associated defects are determined through subsequent analysis

Question 5

Differences between Static Testing and Dynamic Testing

Answer 5

Static testing can be applied to non-executable work products, while dynamic testing can only be applied to executable work products

Question 6

Typical defects that are easier and/or cheaper to find through static testing include:

Answer 6

• Defects in requirements
• Design defects
• Certain types of coding defects
• Deviations from standards
• Incorrect interface specifications
• Specific types of security vulnerabilities
• Gaps or inaccuracies in test basis coverage (e.g., missing tests for an acceptance criterion)

Question 7

Review Process Activities