The word “Agile” itself goes with the meaning “move quickly” and so the testing. In agile testing, no conventional testing practices are applicable to wait until the entire development cycle activities are completed, whereas the testing is closely intact with the development and is done in parallel as and when a piece of code is developed.
Agile Testing has been an evolving methodology we’ve been seeing over the last few years. The popularity of this methodology can be accredited to several reasons such as the product development lifecycles and Go to market cycles (GTM) are shrinking in the light of ever changing business dynamics.
Everyone wants to put the product out in the market as soon as possible capturing the customer share as soon as possible to gain control on the changing business dynamics. Agility, it seems is paying dividends for such short GTMs and providing a quick ROI.
Some of the principles behind the Agile Testing [Reference: Agile Manifesto] are:
Customer satisfaction by rapid agile scrum (sprint) process, continuous delivery of useful software
Working software is delivered frequently (weeks rather than months)
Working software is the principal measure of progress
Even late changes in Testing Requirements are welcomed
Close, daily cooperation between business people and developers
Face-to-face conversation is the best form of communication
Projects are built around motivated individuals, who should be trusted
Continuous attention to technical excellence and good design
Regular adaptation to changing circumstances