Best practices followed to implement Automation in Agile Project


Agile development and testing is rising in popularity and smart QA/testing teams keep pace with current development trends. Agile testing tools vary from project management tools to automated testing tools. 

In contrast, waterfall projects will tend not to invest in automation as a priority, mainly due to the phased investment and handoff mindset that accompanies that approach. At best, builds may leverage some automation, and a phase of a waterfall project may be dedicated to functional test automation for long-term support/future release needs, but it’s rare to find much more in a back-end-loaded waterfall project.

 In Agile the testers are an integral member of the development team, participating entirely in the development process, from design through delivery & deployment. A deep understanding of the domain and features under development is crucial to developing tests that provide meaningful feedback. Testers may also work on numerous stories or features at one time, so tools to organize and manage multiple testing activities are critical. They will have adapted to a more collaborative, team-based approach to the iterative/continuous delivery of high-quality, working software as a measure of progress. 

Most people who work with Agile know that automating system testing is essential, but they also realize that it is very easy to fail in doing so. What makes test automation so hard within the agile framework is that the test object is continuously changing since it is gradually refined over sprints. If there is anything a test automation engineer is scared of, its constant changes and the resulting high level of maintenance. 

In this article, I will be sharing with you some of the test automation techniques which our team successfully implemented on a recent project – the results of which have proven to be a huge asset. 

We have saved around 39hrs of manual effort by implementing automation in our project. 

An agile project without test automation is essentially just a waterfall project in phases.

1 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist

Outline/structure of the Session

graphProblem: We are working in agile project so as we all know we deliver in chunks. Initially it was decided that federal law which was declared by Obama also know as Essential Health benefit or Obama Care and we have started working on Dental product. Initially the requirement is for 2-3 sates a and for one state there are only 9 test cases and time to execute one test case is 15 min so we have decided to go for manual testing as we are getting the stories in chunks. After that we got approval for all the 26 sates, so we have decided why not to automate and we have saved 39 hrs of Manual effort by implementing automation using Selenium.

Learning Outcome

We have saved 39 hours of manual effort by implementing automation.

Target Audience

Anyone can attend the session who is having knowledge of Agile

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Submission