From the Blogosphere
Agile Testing Automation | @DevOpsSummit #DevOps #APM #Microservices
Agile test management has been evolving to be more accommodating to agile processes
By: Sanjay Zalavadia
Mar. 7, 2016 07:30 PM
Four Ways to Improve Your Agile Testing Automation Processes
Agile software development is slowly but surely becoming the norm for a significant contingency of software developers. What used to be rigid, step-by-step processes that were siloed between specific teams have transformed into a collaborative, adaptive methodology that ultimately leads to the creation of superior solutions.
As an integral component of software development, agile test management has also been evolving to be more accommodating to agile processes. Testing automation in particular is still coming into its role as an agile tool and, for some teams, this may create unique challenges. Still, by taking the following into consideration, testing teams can reap all the benefits of testing automation in an agile environment.
1. Strong communication
For the most part, telecommunications and cloud sharing capabilities have made it possible for even disparate testers to stay in touch with each other and with other teams. This communication is essential for fostering agile testing methodologies and must not be shirked. As the experts, test managers can certainly take a leading role in testing automation, but only by collaborating with developers can they have a solid understanding of how to plan for regression tests, and where testing automation needs to occur. The key here is to create a transparent, collaborative testing life cycle.
2. Select the right tools for the job
"Support for automated testing scenarios may be much more useful when using Agile development methodologies rather than support for specified inputs and expected outputs as in traditional automated testing tools," Kannan wrote. "Many more automated tests for scenarios become reusable between iterations, so re-scripting between iterations becomes easier."
3. Automate generously, but intelligently
That said, deciding what tests to automate and how exactly to automate them must be a very hands-on process. These tests don't necessarily have to run manually on the first go-around, but they should be intelligently integrated, which consists of deciding how they should interact with the scripts before they are set in motion. In theory, it's wise to seize every opportunity for test automation. In practice, it's even wiser to make sure that automated tests are thoughtfully deployed and that they rely on test metrics that actually matter.
4. Manual testing isn't going anywhere
The good news here is that if the need for a certain manual test seems to arise more frequently, it can subsequently be automated. Manual testing is great for unique or anomalous user scenarios. But once the need for this test becomes recurring, it may make more sense to automate it, and therein lies the beauty of agile testing methodologies. They're as flexible as you need them to be.
Reader Feedback: Page 1 of 1
Latest Cloud Developer Stories
Subscribe to the World's Most Powerful Newsletters
Subscribe to Our Rss Feeds & Get Your SYS-CON News Live!
SYS-CON Featured Whitepapers
Most Read This Week