Microservices Expo Authors: Elizabeth White, Mehdi Daoudi, Pat Romanski, Flint Brenton, Gordon Haff

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

@DevOpsSummit: Blog Post

Agile Performance Testing | @DevOpsSummit #DevOps #BigData #Microservices

For companies not working in Agile, it's common to spend months writing code without seeing anything functional

Performance Testing in an Agile Environment

There once was a time when testers operated on their own, in isolation. They'd huddle as a group around the harsh glow of dozens of CRT monitors, clicking through GUIs and recording results. Anxiously, they'd wait for the developers in the other room to fix the bugs they found, yet they'd frequently leave the office disappointed as issues were filed away as non-critical. These teams would rarely interact, save for those scarce moments when a coder would wander in needing to reproduce a particularly finicky error.

That was a long time ago (for most of us).

One of the biggest reasons that Agile Development was created in the first place was to improve the quality of software by improving the way software is written. The old communication barriers described above were quickly torn down as the tester's job shifted to validating software, and not finding bugs. That philosophy is represented directly as one of the Agile Manifesto's core principles: Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

For companies not working in Agile, it's common to spend months writing code without seeing anything functional. Agile sought to break that pattern.

Quality Is Everyone's Job
In order to do that, development teams had to change the way they thought about quality. One of the most important ideas that Agile introduced was the idea of done-ness. Code was written until it was complete, functional, and working well - and if you couldn't get a portion of code done in a suitably short timeline, you had to break it up into smaller components that could reach a final state of being done. By following this process, quality would improve.

Now, quality is part of everyone's job - that's the essence of Agile Testing. You can no longer write code in a bubble and throw it over the fence to a tester to make sure it works. You have to take responsibility for the quality of what you are writing, otherwise it isn't done.

As a result, the role of the QA department has become the keeper of that process. QA professionals make sure that the right test automation cases are being written, and that the entire test function is being executed properly across all of the codebase. They monitor test metrics to evaluate howdone everyone's code is, so that when a sprint is completed, the quality bar is met.

But what about performance testing? We've written previously how performance often still remains an afterthought in the test process - even at agile shops. But if performance is not the job of one lone performance engineer or an isolated team, can it be part of everyone's job?

Can the performance testing function become a keeper of a process, as has happened with functional QA?

Of course! Here's how to make that happen.

Share Metrics from Performance Tests
"You get what you measure." It's a common saying that describes how you can motivate behavior simply by tracking and publishing the metrics you seek to influence. It really works, and can be a great way to get everyone on your team sharing the responsibility for the performance of your application. Prepare a report that identifies a few key metrics, and share that with everyone across your Development, QA, and Operations teams. If you really want to go the extra mile, customize that report to fit the needs of each department, by including data that:

  • Helps developers find the root causes of performance problems
  • Assesses task-based performance for UX
  • Embeds performance test results with functional test results for the QA team
  • Highlights inter-component performance for the integration team
  • Positions live data from performance monitoring systems for the operations team

Ask Developers to Write Performance Unit Tests
By now, agile developers are used to writing their own test cases. In fact, if you are a shop that practices Test-Driven Development (TDD), you build your tests even before you write a line of code. But are your developers writing performance test cases? Or are they just writing functional tests?

Load tests and stress tests don't need to be large, all-encompassing tests that put the entire production environment to work at maximum scale. There are a number of ways to write unit tests for performance that can be part of your TDD process, or even added as performance requirements on your agile task board. If your development team is thinking about acceptable performance early in the process, the same way they think about acceptable functionality, you're a lot closer to a truly distributed sense of ownership for application performance.

Run Performance Code Reviews
Code reviews are nothing new, but in Agile Development that have definitely gained a heightened degree of prominence. Whether your team casually asks for a peer's help on an ad-hoc basis, or the practice of reviewing code is rigorously built into the fabric of your development process, getting a second pair of eyes on code can boost code quality significantly. Plus, knowing that someone's going to be looking at what you write may force you to write cleaner, more maintainable code in the first place - an all-around good outcome.

Here's the thing - performance should be a part of whatever code review process you have in place. Your colleagues should be trained to look not only for functional problems and edge-cases, but also for poorly written algorithms and other problems related to scale and optimization. One good technique is to actually have dedicated performance code reviews, where people sit down and review code exclusively for the purposes of finding performance problems. Once again, the more your development team thinks about performance up front, the fewer problems you'll run into on the back end.

Establish Common Performance Test Scenarios Across Departments
Finally, it's important to have everyone speaking the same language. The performance and scalability tests you run should be based on real-world usage and behavioral patterns of your users. That means that performance problems you see in your production environment should be explored and tested thoroughly in development and QA. Similarly, the key pathways that are identified during development as those most likely to bottleneck should be tagged and monitored closely once that software makes its way into the field.

To do this, share a common library of performance test scenarios that can be easily transported between environments. A test that the development team creates should run easily as a simulated user in a live production environment. And a user path that the Ops team is monitoring should be easily testable in a structured continuous integration process. That's why a shared test scenario library is so important, and why we've built that into NeoLoad and NeoSense.

It Takes a Village
No man is an island, nor is any performance engineer. Your entire application team shares the responsibility for keeping applications running fast and responsively, and by following the guidelines above, you can help them accept that responsibility. Encourage everyone to pay attention to your application's performance, and you can play an active role in advancing your organization's culture of quality.

Photo Credit: By Packer, poster artist, Artist (NARA record: 8467744) (U.S. National Archives and Records Administration) [Public domain], via Wikimedia Commons

More Stories By Tim Hinds

Tim Hinds is the Product Marketing Manager for NeoLoad at Neotys. He has a background in Agile software development, Scrum, Kanban, Continuous Integration, Continuous Delivery, and Continuous Testing practices.

Previously, Tim was Product Marketing Manager at AccuRev, a company acquired by Micro Focus, where he worked with software configuration management, issue tracking, Agile project management, continuous integration, workflow automation, and distributed version control systems.

@MicroservicesExpo Stories
"We started a Master of Science in business analytics - that's the hot topic. We serve the business community around San Francisco so we educate the working professionals and this is where they all want to be," explained Judy Lee, Associate Professor and Department Chair at Golden Gate University, 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.
For over a decade, Application Programming Interface or APIs have been used to exchange data between multiple platforms. From social media to news and media sites, most websites depend on APIs to provide a dynamic and real-time digital experience. APIs have made its way into almost every device and service available today and it continues to spur innovations in every field of technology. There are multiple programming languages used to build and run applications in the online world. And just li...
There is a huge demand for responsive, real-time mobile and web experiences, but current architectural patterns do not easily accommodate applications that respond to events in real time. Common solutions using message queues or HTTP long-polling quickly lead to resiliency, scalability and development velocity challenges. In his session at 21st Cloud Expo, Ryland Degnan, a Senior Software Engineer on the Netflix Edge Platform team, will discuss how by leveraging a reactive stream-based protocol,...
The general concepts of DevOps have played a central role advancing the modern software delivery industry. With the library of DevOps best practices, tips and guides expanding quickly, it can be difficult to track down the best and most accurate resources and information. In order to help the software development community, and to further our own learning, we reached out to leading industry analysts and asked them about an increasingly popular tenet of a DevOps transformation: collaboration.
We call it DevOps but much of the time there’s a lot more discussion about the needs and concerns of developers than there is about other groups. There’s a focus on improved and less isolated developer workflows. There are many discussions around collaboration, continuous integration and delivery, issue tracking, source code control, code review, IDEs, and xPaaS – and all the tools that enable those things. Changes in developer practices may come up – such as developers taking ownership of code ...
The dynamic nature of the cloud means that change is a constant when it comes to modern cloud-based infrastructure. Delivering modern applications to end users, therefore, is a constantly shifting challenge. Delivery automation helps IT Ops teams ensure that apps are providing an optimal end user experience over hybrid-cloud and multi-cloud environments, no matter what the current state of the infrastructure is. To employ a delivery automation strategy that reflects your business rules, making r...
Cloud Governance means many things to many people. Heck, just the word cloud means different things depending on who you are talking to. While definitions can vary, controlling access to cloud resources is invariably a central piece of any governance program. Enterprise cloud computing has transformed IT. Cloud computing decreases time-to-market, improves agility by allowing businesses to adapt quickly to changing market demands, and, ultimately, drives down costs.
Modern software design has fundamentally changed how we manage applications, causing many to turn to containers as the new virtual machine for resource management. As container adoption grows beyond stateless applications to stateful workloads, the need for persistent storage is foundational - something customers routinely cite as a top pain point. In his session at @DevOpsSummit at 21st Cloud Expo, Bill Borsari, Head of Systems Engineering at Datera, explored how organizations can reap the bene...
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.
"CA has been doing a lot of things in the area of DevOps. Now we have a complete set of tool sets in order to enable customers to go all the way from planning to development to testing down to release into the operations," explained Aruna Ravichandran, Vice President of Global Marketing and Strategy at CA Technologies, 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.
"We are an integrator of carrier ethernet and bandwidth to get people to connect to the cloud, to the SaaS providers, and the IaaS providers all on ethernet," explained Paul Mako, CEO & CTO of Massive Networks, 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.
"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.
"NetApp's vision is how we help organizations manage data - delivering the right data in the right place, in the right time, to the people who need it, and doing it agnostic to what the platform is," explained Josh Atwell, Developer Advocate for NetApp, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
"Outscale was founded in 2010, is based in France, is a strategic partner to Dassault Systémes and has done quite a bit of work with divisions of Dassault," explained Jackie Funk, Digital Marketing exec at Outscale, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
"I focus on what we are calling CAST Highlight, which is our SaaS application portfolio analysis tool. It is an extremely lightweight tool that can integrate with pretty much any build process right now," explained Andrew Siegmund, Application Migration Specialist for CAST, 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.
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...
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...
Cavirin Systems has just announced C2, a SaaS offering designed to bring continuous security assessment and remediation to hybrid environments, containers, and data centers. Cavirin C2 is deployed within Amazon Web Services (AWS) and features a flexible licensing model for easy scalability and clear pay-as-you-go pricing. Although native to AWS, it also supports assessment and remediation of virtual or container instances within Microsoft Azure, Google Cloud Platform (GCP), or on-premise. By dr...
With continuous delivery (CD) almost always in the spotlight, continuous integration (CI) is often left out in the cold. Indeed, it's been in use for so long and so widely, we often take the model for granted. So what is CI and how can you make the most of it? This blog is intended to answer those questions. Before we step into examining CI, we need to look back. Software developers often work in small teams and modularity, and need to integrate their changes with the rest of the project code b...
Kubernetes is an open source system for automating deployment, scaling, and management of containerized applications. Kubernetes was originally built by Google, leveraging years of experience with managing container workloads, and is now a Cloud Native Compute Foundation (CNCF) project. Kubernetes has been widely adopted by the community, supported on all major public and private cloud providers, and is gaining rapid adoption in enterprises. However, Kubernetes may seem intimidating and complex ...