thought leadership webinar: agile automation testing means agile challenges
TRANSCRIPT
Agile Automation Testing Means Agile Challenges
Agile Automation Testing – What is it?
Applying agile development principles to automation testing is called Agile Automation Testing. The whole bunch of tester are divided into smaller teams and by applying varied technologies (mostly open source technologies) automation scripts are generate. Ideally these automation projects should be completed in a weeks time. Sprint to sprint automation testing is preferred.
Challenges in achieving Agile Automation Testing
Organizations find it difficult to provide the required attention and time for testing - especially in the Agile world. The Leading industry analysts and experts feel that ‘Agile Automation Testing’ could be the answer to this challenge. But Agile Automation Testing has its own challenges.
Challenge 1: Changing requirementsChallenge 2: Selecting the right tool(s)Challenge 3: Identifying the right resourceChallenge 4: Growing need of regression testing for each sprintChallenge 5: Communication across teamsChallenge 6: Effectiveness of scrum meetingsChallenge 7: Training
How to overcome these ‘Agile’ challenges?
Consider the following to overcome challenges in agile automation testing. Proper planning Identifying a tool which can be used by existing testers Effective communication Validating automation scripts Have required scripts ready for each sprint
Benefits Vs. Pitfalls
Benefits:• The Whole Team is Responsible for Quality• Better Communication• Defects are Easy to Fix• Flexibly Incorporate New Requirements• Testing Can’t Be Cut
Pitfalls:• Sprint becoming mini-waterfall• Unit tests not automated• Automation frameworks not customized
Vendor selection criterion
We should be considering the following points while selecting a tool for automation.• If the tool/framework suits the requirement.• If the tool/framework can be used readily.• Do we have the right resources who are capable of using the tool/framework.• Can we use existing resources to work with the tool/framework.• Initial time investment required to implement the tool or framework.• Training time required for resources on the tool/framework.• Turn around time of testing using the tool.• ROI of the tool.
Click here to watch the recording
Q & A
