Based on the implementation of testing and knowledge gained through reading of related articles

following difference are summarized. However there could be difference of opinion. Any
suggestions to add-on to this is welcome

V-Model
• Unit and Integration are separate and linear phases, so testing starts after development is
completed
• Generally the Unit testing is white box and done by software developers
• Test scenarios are prepared for different tests using different SDLC documentation. E.g.
system design is prepared using functional and technical design doc
• Testing starts early, but Identification of defects is delayed and fixing is more expensive
e.g. since UAT is based on requirement doc and that is done in the end any defects
found/fixed during UAT is expensive, this is universally agreed as defects found in later
phase of development cycle are more expensive to fix.
• Since the application is ready and documents are generally updated, comparatively
domain knowledge is not required
• For COTS(Commercial off the shelf) software the documents as per v-model is not
available , hence may not be able to follow procedures of the model.
• V-model discourages active user involvement in evaluating the design, and especially the
interface, before the formal user acceptance testing stage
Agile Model
• Unit and Integration is run in parallel to development
• Unit testing is mostly black box and done by testers
• Test Scenarios/test cases are prepared upfront from all SDLC documentation and tested
in all cycles(SIT, UAT)
• Regression testing takes place in each cycle.
• Testing starts as early as practical and proceeds continuously throughout the lifecycle ,
defects are detected early
• Agile testing needs domain knowledge as the test is done before and while the application
development in progress