The V-model is a software development process (also applicable to hardware development) which can be presumed to be the extension of the waterfall model. Instead of moving down in a linear way, the process steps are bent upwards after the coding phase, to form the typical V shape. The V-Model demonstrates the relationships between each phase of the development life cycle and its associated phase of testing. The horizontal and vertical axes represents time or project completeness (left-to-right) and level of abstraction (coarsest-grain abstraction uppermost), respectively.
Agile testing is a software testing practice that follows the principles of the agile manifesto, emphasizing testing from the perspective of customers who will utilize the system. Agile testing does not emphasize rigidly defined testing procedures, but rather focuses on testing iteratively against newly developed code until quality is achieved from an end customer's perspective. In other words, the emphasis is shifted from "testers as quality police" to something more like "entire project team working toward demonstrable quality."
The Word Agile means "Moving Quickly" and this explains the whole concept of Agile Testing. Testers have to adapt to rapid deployment cycles and changes in testing patterns.
Agile testing involves testing from the customer perspective as early as possible, testing early and often as code becomes available and stable enough from module/unit level testing.
V model is validate model where we got the client requirement in one go and Development and QA activities starts together from starting of the project. Requirement Phase we create UAT Scripts on the basis of Business Requirements, High level design we do System testing, Low level design we do integration testing coding and unit testing.
Where in Agile methodology, client gives requirement in bits and pieces and we do development in iterative method. Where they can update their requirement in next iteration and generally we adopt TDD approach for development. There are regular scrub calls and flexible. And many more...
Thanks a lot for all of you for commenting on the "Agile" Vs "V-Model" discussion.
This is really helpful, specially for someone like me, who has not yet worked in any Agile environment but wish to have knowledge for the same. Of course from interview perspective this is really very helpful.. Keep it up guys... !!