Agile testing is a software testing practice which follows agile software development principle. It involves all members of a cross-functional agile team, with special expertise contributed by different testers. Agile testing is an iterative testing method, and it requires collaborations between the customer and self-organising team and aligns development with customer needs.
So how agile testing is working?
(Pic from https://www.tutorialspoint.com/agile_testing/agile_testing_methodologies.htm)
So, here, for each iteration, an integrated working product increment has resulted, and the result is delivered for User Acceptance Testing (UAT).
Continuous integration is the key of Agile. Unlike traditional Waterflow model, Agile requires a depth of continuous collaboration between stakeholders of a project, including managers, developers, testers, and customers.
Why do organisations prefer Agile methodology over Waterfall or any other methodologies?
Comparing with traditional testing methodologies, Agile Testing saves time and money, and requires less documentation. The regular meetings of Agile Testing can also help determine the issues or upcoming problems well in advance. Also, the company, or the team of the software system can receive regular feedbacks from the end users.
In contrast, traditional waterfall model treats analysis, design, coding, and testing as discrete phases in a software project. When we are in the second stage, it is impossible for us to go back to the previous stage. (1) It can cause poor quality when the project runs out of time and money, and testing is the only phase left to do. Under this situation, the testing phase will be cut off. (2) Also poor visibility. We will never know where we are when we are doing a waterfall project. (3) Also, it is quite risky. Too late to go back.