Chapter 3 - Static Testing Flashcards
(15 cards)
What is static testing?
Testing that evaluates work products without executing the software.
What are two types of static testing?
Reviews and static analysis.
Why is static testing important?
It finds defects early, saves cost, and improves quality before code is run.
What is a key difference between static and dynamic testing?
Static testing doesn’t involve executing code; dynamic testing does.
Give three examples of work products that can be examined in static testing.
Requirements, design documents, source code, test cases, models.
What is an informal review?
An unstructured, quick check for obvious issues; no formal process.
What is a walkthrough?
A review where the author leads others through the work product to gather feedback.
What is a technical review?
A structured review where technical experts evaluate the quality and correctness of the work product.
What is an inspection?
A formal, structured review with roles, checklists, and logs—used in high-assurance environments.
What roles are common in formal reviews?
Author, reviewer, moderator, scribe (and optionally, a manager).
What are the six stages of a formal review (e.g., inspection)?
Planning → Kick-off → Preparation → Review Meeting → Rework → Follow-up.
What is static analysis?
Automated analysis of code or models without executing them.
Name three things static analysis can detect.
Coding standard violations, security vulnerabilities, uninitialized variables, dead code.
Give two benefits of static analysis.
Catches defects early; enforces coding standards.
Give one limitation of static analysis.
It may produce false positives and can’t find runtime issues.
