Over a million developers have joined DZone.

Using Crowdtesting to Build More Agile Regression Testing Processes for Legacy Code

DZone's Guide to

Using Crowdtesting to Build More Agile Regression Testing Processes for Legacy Code

QA testing, especially with legacy code bases, can be a time consuming process. Read the story of how one company made their QA Agile.

· Agile Zone ·
Free Resource

Adopting a DevOps practice starts with understanding where you are in the implementation journey. Download the DevOps Transformation Roadmap. Brought to you in partnership with Techtown.

For many teams, testing processes can’t keep up with development speed. This is especially true for teams that maintain legacy code bases, which are prone to regressions and must be carefully checked before each deployment. Finding a solution that balances reliable results with the speed and scalability that Agile teams need to stay competitive can be a challenge. Here’s how PerformanceCentre found a solution to their regression testing roadblock by leveraging crowdtesting.

The Situation: Moving Fast While Managing Legacy Code

PerformanceCentre offers a SaaS platform for sales teams to calculate commissions. Their functionality has been built up over the past decade. As with many products with a significant amount of legacy code, regression testing is a critical component of every release. As a result, PerformanceCentre runs as many as 300 regression test cases for each two-week sprint.

The Problem: Finding a Regression Testing Solution That Fits

Manual execution of PerformanceCentre’s regression test suite required up to 2 weeks of working hours, which puts a strain on their lean technical team (4 developers and 1 tester). Finding an alternative to manually executing regression tests was critical to maintaining their deployment cadence without losing the coverage they needed.

While the team made an attempt at shifting to automation, creating and managing automated tests still required a significant amount of PerformanceCentre’s resources, without offering the reliable results they needed. The team considered opting for traditional outsourcing or hiring another test engineer in-house, but neither solution offered the speedy results that PerformanceCentre required to keep pace with their development sprints.

The Solution: Crowdtesting to Keep Regression Testing Moving Fast

PerformanceCentre landed on crowdtesting as an alternative to traditional QA solutions. Because crowdtesting allows developers to tap into a huge network of trusted software testers, PerformanceCentre can run multiple tests simultaneously, completing their 2-week backlog of tests in around 30 minutes.

By relying on a crowdtesting platform, PerformanceCentre is able to outsource the work of regression testing to the crowd and reduce the amount of testing their team must do in-house. The results they get are not only fast but reliable, with minimal false positives, which gives PerformanceCentre more confidence in the quality of their code. Performance Centre can now release code the day after each sprint ends.

Check out this presentation from Technical Director Marc Fasel to learn more about PerformanceCentre’s journey from manual testing to Agile testing using the crowd. In this deck, Marc covers why he chose crowdsourced testing solutions, and what the results have been.

Take Agile to the next level with DevOps. Learn practical tools and techniques in the three-day DevOps Implementation Boot Camp. Brought to you in partnership with Techtown.

agile ,crowdtesting ,qa

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}