Application performance testing is shifting left – and with good reason. Studies show that making testing an integral part of the Agile development process can boost application quality and performance, while reducing time to deployment. To successfully navigate the shift left in testing, though, you’ve got to get the fundamentals right. And that includes the technology you use. In our last blog, we introduced the Center of Developer Excellence (CoDE), our vision for how the Test Center of Excellence (CoE) can address the disconnect between continuous software delivery trends and current test processes. In today’s blog, we share the impactful way you can bring your CoDE to life.
Do new, without throwing out the old.
Most developers now rely on open source tools like Apache JMeter™ to support the breakneck pace of their work. But unfortunately, many test centers are still wedded to proprietary testing platforms that aren’t optimized for today’s open source technologies. This disconnect has consequences.
Rather than supporting continuous software development and delivery at speed for Agile development teams, Test CoEs are inundated with work that is causing costly bottlenecks and delays. The traditional central IT function becomes a victim of circumstances in Agile development and DevOps delivery and is simply overwhelmed by the velocity-volume-variety of application releases. There simply is no good way to share proprietary QA components and processes with open source-based test scripts or plans as they move from project to project. Each time QA testers take up a new development project, they have to reinvent the wheel.
As a result, companies locked into proprietary test tools face a lose-lose situation. They can slow down release velocity to ensure quality, or they accept more production defects and get to market faster. It’s no way to run a modern software development factory, as discussed in detail in a recent webinar with Forrester. Click here to learn more, on how to avoid the heartaches of broken applications.
Moving to open source is easier than you think.
The very first step in ensuring the ongoing relevance of your Test CoE is to solve this technology disconnect. It starts with the way you bridge your current QA platform with today’s open source testing tools – helping you speak the “language” of your development teams and keep up with demand.
Today, open source testing platforms are mostly SaaS-based, so it’s simple and cost-effective to make the move. Instead of getting locked into costly licenses, you pay for the testing resources you consume as projects come and go. This also means you preserve your investment in your current test scripts.
My colleagues at BlazeMeter, for example, have built a free, automated tool to convert your current LoadRunner VuGen and TruClient tests to open source. If you can copy and paste, you’re in business. Your converted tests can be run on a high-reliability, enterprise-grade platform in the cloud, whenever and wherever you want. You can even run tests automatically as part of your continuous integration/continuous delivery process – triggered by an API or CLI as developers check code or run builds. If you are using a traditional test platform today, e.g. LoadRunner, watch this webinar to understand why shifting your test left to democratize your testing is easier than you think.
Broker and bridge for application testing in the cloud.
Adopting open source performance testing lets you immediately unlock lots of new value for your business. You can scale on demand and become an effective broker of the test resources your developers need. You can be the automation and integration hub that stands up test resources on demand and helps to run tests in parallel to eliminate wait time. You can optimize use of test resources across distributed teams to minimize waste immediately.
You also get the best of both worlds. As you decentralize testing, your Agile development teams can put their code through its paces as they work. And you can use the same open source tools to achieve new centralized visibility into the many development projects underway across the business. You can bridge these enterprise-ready, SaaS-based testing services for Agile development teams and their Agile release trains in dedicated workspaces that coexist seamlessly with the traditional Test CoEs. In the meanwhile, your current on-premises test platform continues to take on its existing charter and performs wider systems tests for large and complex, epic solution trains across the business.
Be open source, enterprise ready for CoDE.
As you bridge and broker application testing services across the many distributed teams in your organization, remember to pick up on best practices for Agile development and DevOps delivery that can augment your traditional Test CoE and help you evolve to a Center of Developer Excellence (CoDE).
In CoDE, QA issues and bottlenecks have nowhere to hide. You can monitor KPIs, quality metrics and testing resources consumed – all on a single dashboard. You can spot overarching quality issues and can determine where additional test resources are needed.
To understand how easy it is to use of open source testing tools like JMeter in your current LoadRunner environment, join us as we provide hands-on, practical examples of how to get up and running quickly with JMeter. Ultimately, you can do more and do it faster – solidifying your test organization’s role.
Open source, enterprise ready tools are fundamental to the future relevance of any centralized testing team. Once you have them, you can take other impactful steps to ensure your test team’s ongoing value. Visit us on our webpage (www.blazemeter.com/shiftleft) to take your first steps in shifting testing left and to give BlazeMeter a try – for free. In the meantime, tell us what you think about the disruptive forces faced by your test CoE by completing this simple survey. We will email you our findings once the survey is complete.
You might also find these useful:
Interested in writing for our Blog?Send us a pitch!