Chapter 3 • 80 minutes
Static Testing
Reviewing work products without executing them: types of reviews, the review process, roles and responsibilities, and the value of finding defects early.
3.1 Static Testing Basics
Static testing examines work products without executing the code. It includes reviews (manual) and static analysis (tool-supported).
Products That Can Be Statically Tested
- Requirements, user stories, acceptance criteria
- Architecture and design specifications
- Source code, test cases, test scripts, user manuals, contracts, project plans, models
Value of Static Testing
- Detects defects early (cheaper to fix)
- Identifies defects not easily found by dynamic testing (e.g. requirement ambiguities)
- Improves consistency and quality of work products
- Improves productivity and reduces development cost and time
- Spreads knowledge through the team
Static vs Dynamic Testing
Both find defects, but static works without execution and can find defects in non-executable work products. Dynamic requires execution and finds failures caused by defects. They are complementary.
3.2 Feedback and Review Process
Activities of the Review Process
- Planning — define scope, criteria, effort, type of review.
- Review initiation — distribute work product, explain context, allocate roles.
- Individual review — each reviewer examines the work product and notes issues.
- Issue communication and analysis — discuss issues, decide on disposition, record agreed actions.
- Fixing and reporting — author fixes issues; results reported against criteria.
Roles in a Formal Review
- Manager — decides resources, schedules; not always at meeting.
- Author — creator/maintainer of the work product.
- Moderator (facilitator) — runs the review meeting, mediates.
- Scribe — records issues and decisions.
- Reviewer — examines the work product and reports findings.
- Review leader — overall responsibility for the review.
Review Types
- Informal — no formal process, minimal documentation. Cheap.
- Walkthrough — led by author; scenario, dry-run; mainly for learning and finding defects.
- Technical review — peers/technical experts, documented, may have a facilitator.
- Inspection — most formal; defined roles, metrics, formal entry/exit criteria, defect logging.
Review Techniques
Ad hoc, checklist-based, scenario-based, role-based, perspective-based reading.
Success Factors
Clear objectives, right people, blame-free culture, small chunks, sufficient time, management support, training, and follow-up on findings.