Overview
Mapping Development to Testing
The V-Model is a highly disciplined model that mandates that for every development activity, there is a corresponding testing activity.
Although often associated with 'Waterfall,' the principles of the V-Model apply to Agile too. It visualizes the 'Mirror' relationship between stages: for example, Acceptance Testing validates the original Requirements, while Unit Testing validates the low-level Design.
Best Practices
Dos and Don'ts
Avoid common mistakes that can lead to flaky tests and maintenance nightmares.
What to do
- •Use the V-Model to ensure 100% traceability between requirements and tests.
- •Start planning your Acceptance tests while the Requirements are being written.
- •Maintain a clear link between technical specs and integration tests.
Common Pitfalls
- •Don't follow the V-Model too rigidly in fast-paced startup environments; it can become overly bureaucratic.
- •Don't wait to reach the bottom of the V (code) before you start the verification work on the left side.
The Details
The Logic of Parallel Planning
The true value of the V-Model is Parallel Planning. It suggests that the moment you define a Business Requirement, you should also be defining the Acceptance Test for it. This ensures that the requirements are 'testable' from the start, preventing 'Requirement Ambiguity'—one of the most common and expensive sources of production bugs.