“There have been ups and downs in implementing change [to an automated DevOps approach]. Especially around collaboration where so many teams are working in silos with their own set of tools and processes. Sharing knowledge between teams wasn’t happening, and collaboration with the business was limited. All of this was delaying releases. The QA team didn’t have enough time to test, and if they found a problem, developers didn’t have enough time to fix it,” says the company’s Director of Information Technology Services.
The company went to smaller release cycles so they could test earlier and resolve issues faster. They used automation to break down the silos by going to a self-service model where DevOps teams could do their own testing.
Continuous testing was a critical element in the company’s automation journey, the director notes. “We automated all testing,” she says. “But teams were using many different [testing] tools. Some were using open source, others were using legacy tools that took hours to build and run tests. So we wanted a standard tool that followed a standard approach. And for us, that was NeoLoad.”
The advantage of NeoLoad is that it is equally effective for different types of applications (web, packaged enterprise apps, etc.), different kinds of tests (unit testing, end-to-end testing), and different teams of various skill levels (expert performance testers, non-expert developers). With NeoLoad, the company brought everything under one umbrella and kicked off testing as part of a Jenkins pipeline. With the NeoLoad-Dynatrace integration, the company has the data from both its NeoLoad custom dashboards and from the Dynatrace monitoring.
“If there’s a problem in the code or there are infrastructure issues or an API is breaking because of some backend services, we are able to debug very fast. Plus, we are able to provide stakeholders with the pass/fail results — or whatever information they need — using NeoLoad dashboards, very early in the lifecycle,” the director says.