Agile Model Over Waterfall Model Case Study

1. Abstract

Agility basically means the power of being AGILE i.e. the art of moving quickly and seamlessly with proper balance, speed and coordination. This definition of agility can be applied to testing as well. Agile testing can be considered as the software testing methodology which does not follow testing practices and procedures. This is basically defined as RAPID TESTING where strategies to test the functionality does not follow any procedure.

2. Introduction

Agile Testing is a testing approach which follows iterative and incremental model i.e. the agile team has to forge ahead with such a mindset that they have to prepare themselves for production deployment(to deliver results) almost every two weeks. Instead of setting huge goals,
Difference between Traditional and Agile way

In agile team, every team member has decision making power which is not present in traditional way. So the whole team is responsible for the final outcome.

Development and Testing are clubbed into one single phase. Developers are feedback infected i.e. they seek for feedback every time they develop a phase in order to deliver high quality product to customer.

4. Advantages of Agile Model over Waterfall Model

• Agile model is adaptable to change i.e. after implementation; changes can be made easily which is not possible in case of Waterfall model.

• Bugs can be found easily as one has a READY TO LAUNCH product at the end of tested phase whereas in Waterfall model, testing is done at the very end so the bugs are found at the end.

• In agile approach, better object oriented processes are followed so the product is ready to be deployed on production well within timelines but in waterfall model, there is only one major release which is a major challenge.

5. AGILE TESTING ≠ EXPLORATORY TESTING

Agile Testing cannot be considered as Exploratory Testing. But conversely, exploratory testing can be considered as agile way of
Key Points
TDD (Test Driven Development) - It is the important term wherever the agile teams are formed. TDD is basically writing the test cases before the actual development starts. This method helps in reducing the bugs as with this approach there is less chance of developer missing any requirement and also it forces the developer to do UNIT TESTING every time before they actually release the code.
ATDD (Acceptance Test Driven Development) - It is an approach in which UAT (User Acceptance tests) are written before the actual development starts. The main purpose of doing this is to involve the business so that they give the go ahead after analysing UAT so that while in development phase, no requirement slippage takes place.
Automate Regression Testing - This point is very important as agile teams used to work with high agility so time is the key factor. In order to save time, automation of regression suite is very important as regression of functionalities needs to perform on regular basis, by automating this step, a lot of time can be