Overview
Checking the Blueprint
Verification is the proactive side of the 'V' model. It ensures that the team doesn't start building a feature based on flawed logic or incomplete specs.
For QA Managers, verification is the ultimate Shift-Left activity. By performing 'Static Testing' on requirements and architecture, you can catch up to 60% of potential defects before a single line of code is written.
Best Practices
Dos and Don'ts
Avoid common mistakes that can lead to flaky tests and maintenance nightmares.
What to do
- •Perform Peer Reviews on all Test Plans and Automation Scripts.
- •Check that requirements are 'SMART' (Specific, Measurable, Achievable, Relevant, Time-bound).
- •Use checklists to ensure consistency during inspections.
Common Pitfalls
- •Don't skip verification just because you are in an Agile 'rush'.
- •Don't confuse verification with validation; you can verify a product that is perfectly built but ultimately useless to the user.
The Details
Static Testing: The Low-Cost Hero
Verification is often overlooked because it doesn't involve 'running tests'. However, Static Analysis is the most cost-effective way to improve quality. Catching a requirement ambiguity in a 'Three Amigos' meeting costs nothing compared to fixing that same logic error in production. Verification builds the foundation of 'Correctness' upon which all subsequent code is built.