Welcome!

Microservices Expo Authors: Stackify Blog, Aruna Ravichandran, Dalibor Siroky, Kevin Jackson, PagerDuty Blog

Related Topics: @DevOpsSummit, Microservices Expo, Linux Containers, Containers Expo Blog

@DevOpsSummit: Article

Agile Testing Automation | @DevOpsSummit #DevOps #APM #Microservices

Agile test management has been evolving to be more accommodating to agile processes

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
Contrary to the notion of an open workspace in which different teams freely walk up to one another with observations and questions, many testing teams still work in different offices, sometimes even in different parts of the world. According to TechTarget contributor Francis Miers, nearly 60 percent  of all agile testing teams are scattered across the map. On the surface, this may seem contradictory. However, the problem with traditional testing methodologies was not that people weren't working in the same room, but that they weren't communicating effectively. As a result, teams were relatively blind to what happened to a product before and after it ended up on their rotation.

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
Trying to use waterfall testing tools for an agile project is like trying to fit a square peg in a round hole: Even if you somehow manage to do it, corners will have to be cut, and the end result won't be ideal. It is for this reason that TechTarget contributor Nari Kannan recommended leveraging testing tools that can accommodate the speed of agile. This includes the ability for scripts to be written and revised swiftly in order to support each new iteration of the project. Kannan also pointed out that agile testing methodologies should be imbued with the ability to test for scenarios rather than standard, black and white inputs.

"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
Everything that can be automated should be automated - assuming it makes sense to automate it. The majority of regression tests, for instance, are inherently redundant. They ensure that an alteration or add-on will play nice with everything that came before it, and this allows for innovation on the fly. Automation integration saves time here by eliminating the need to manually go back through the steps every time changes are applied. In addition to guaranteeing that regression tests actually happen, the risk of human error is significantly reduced.

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
Going off number three, it won't always make sense to automate every test case. Even with exploratory testing that can help testers probe for possible outcomes of specific scenarios, there will be situations in which unforeseen manual testing will be the only sure-fire way to thoroughly vet certain software features. This is especially true when it comes to optimizing the user experience. Even with adaptive design and smarter navigation, the ever-increasing number of platforms, particularly in the form of mobile devices, may result in clunky UX that an automated test cannot readily detect.

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.

More Stories By Sanjay Zalavadia

As the VP of Client Service for Zephyr, Sanjay Zalavadia brings over 15 years of leadership experience in IT and Technical Support Services. Throughout his career, Sanjay has successfully established and grown premier IT and Support Services teams across multiple geographies for both large and small companies.

Most recently, he was Associate Vice President at Patni Computers (NYSE: PTI) responsible for the Telecoms IT Managed Services Practice where he established IT Operations teams supporting Virgin Mobile, ESPN Mobile, Disney Mobile and Carphone Warehouse. Prior to this Sanjay was responsible for Global Technical Support at Bay Networks, a leading routing and switching vendor, which was acquired by Nortel. He has also held management positions in Support Service organizations at start-up Silicon Valley Networks, a vendor of Test Management software, and SynOptics.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@MicroservicesExpo Stories
How is DevOps going within your organization? If you need some help measuring just how well it is going, we have prepared a list of some key DevOps metrics to track. These metrics can help you understand how your team is doing over time. The word DevOps means different things to different people. Some say it a culture and every vendor in the industry claims that their tools help with DevOps. Depending on how you define DevOps, some of these metrics may matter more or less to you and your team.
For many of us laboring in the fields of digital transformation, 2017 was a year of high-intensity work and high-reward achievement. So we’re looking forward to a little breather over the end-of-year holiday season. But we’re going to have to get right back on the Continuous Delivery bullet train in 2018. Markets move too fast and customer expectations elevate too precipitously for businesses to rest on their laurels. Here’s a DevOps “to-do list” for 2018 that should be priorities for anyone w...
If testing environments are constantly unavailable and affected by outages, release timelines will be affected. You can use three metrics to measure stability events for specific environments and plan around events that will affect your critical path to release.
In a recent post, titled “10 Surprising Facts About Cloud Computing and What It Really Is”, Zac Johnson highlighted some interesting facts about cloud computing in the SMB marketplace: Cloud Computing is up to 40 times more cost-effective for an SMB, compared to running its own IT system. 94% of SMBs have experienced security benefits in the cloud that they didn’t have with their on-premises service
DevOps failure is a touchy subject with some, because DevOps is typically perceived as a way to avoid failure. As a result, when you fail in a DevOps practice, the situation can seem almost hopeless. However, just as a fail-fast business approach, or the “fail and adjust sooner” methodology of Agile often proves, DevOps failures are actually a step in the right direction. They’re the first step toward learning from failures and turning your DevOps practice into one that will lead you toward even...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
While walking around the office I happened upon a relatively new employee dragging emails from his inbox into folders. I asked why and was told, “I’m just answering emails and getting stuff off my desk.” An empty inbox may be emotionally satisfying to look at, but in practice, you should never do it. Here’s why. I recently wrote a piece arguing that from a mathematical perspective, Messy Desks Are Perfectly Optimized. While it validated the genius of my friends with messy desks, it also gener...
The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
The next XaaS is CICDaaS. Why? Because CICD saves developers a huge amount of time. CD is an especially great option for projects that require multiple and frequent contributions to be integrated. But… securing CICD best practices is an emerging, essential, yet little understood practice for DevOps teams and their Cloud Service Providers. The only way to get CICD to work in a highly secure environment takes collaboration, patience and persistence. Building CICD in the cloud requires rigorous ar...
The enterprise data storage marketplace is poised to become a battlefield. No longer the quiet backwater of cloud computing services, the focus of this global transition is now going from compute to storage. An overview of recent storage market history is needed to understand why this transition is important. Before 2007 and the birth of the cloud computing market we are witnessing today, the on-premise model hosted in large local data centers dominated enterprise storage. Key marketplace play...
The cloud revolution in enterprises has very clearly crossed the phase of proof-of-concepts into a truly mainstream adoption. One of most popular enterprise-wide initiatives currently going on are “cloud migration” programs of some kind or another. Finding business value for these programs is not hard to fathom – they include hyperelasticity in infrastructure consumption, subscription based models, and agility derived from rapid speed of deployment of applications. These factors will continue to...
Some people are directors, managers, and administrators. Others are disrupters. Eddie Webb (@edwardawebb) is an IT Disrupter for Software Development Platforms at Liberty Mutual and was a presenter at the 2016 All Day DevOps conference. His talk, Organically DevOps: Building Quality and Security into the Software Supply Chain at Liberty Mutual, looked at Liberty Mutual's transformation to Continuous Integration, Continuous Delivery, and DevOps. For a large, heavily regulated industry, this task ...
Following a tradition dating back to 2002 at ZapThink and continuing at Intellyx since 2014, it’s time for Intellyx’s annual predictions for the coming year. If you’re a long-time fan, you know we have a twist to the typical annual prediction post: we actually critique our predictions from the previous year. To make things even more interesting, Charlie and I switch off, judging the other’s predictions. And now that he’s been with Intellyx for more than a year, this Cortex represents my first ...
"Grape Up leverages Cloud Native technologies and helps companies build software using microservices, and work the DevOps agile way. We've been doing digital innovation for the last 12 years," explained Daniel Heckman, of Grape Up in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
The Toyota Production System, a world-renowned production system is based on the "complete elimination of all waste". The "Toyota Way", grounded on continuous improvement dates to the 1860s. The methodology is widely proven to be successful yet there are still industries within and tangential to manufacturing struggling to adopt its core principles: Jidoka: a process should stop when an issue is identified prevents releasing defective products
We seem to run this cycle with every new technology that comes along. A good idea with practical applications is born, then both marketers and over-excited users start to declare it is the solution for all or our problems. Compliments of Gartner, we know it generally as “The Hype Cycle”, but each iteration is a little different. 2018’s flavor will be serverless computing, and by 2018, I mean starting now, but going most of next year, you’ll be sick of it. We are already seeing people write such...
Defining the term ‘monitoring’ is a difficult task considering the performance space has evolved significantly over the years. Lately, there has been a shift in the monitoring world, sparking a healthy debate regarding the definition and purpose of monitoring, through which a new term has emerged: observability. Some of that debate can be found in blogs by Charity Majors and Cindy Sridharan.
It’s “time to move on from DevOps and continuous delivery.” This was the provocative title of a recent article in ZDNet, in which Kelsey Hightower, staff developer advocate at Google Cloud Platform, suggested that “software shops should have put these concepts into action years ago.” Reading articles like this or listening to talks at most DevOps conferences might make you think that we’re entering a post-DevOps world. But vast numbers of organizations still struggle to start and drive transfo...
Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.