Applause’s Bug Fix Verification: Speed Up Your Development Velocity

Dan CagenDan Cagen
minute read

How Applause closes the loop to verify your bug fixes — and enables a CI workflow with a streamlined process

After your Engineering team addresses a problematic bug, how do you ensure that the bug is completely and soundly fixed, and won’t cause your customers any issues in the future?

Closing this loop is a key portion of QA testing, and Applause believes it’s important to rely on the source that found the bug originally to validate that the bug is 100% fixed. If the teams of QA testers that identified the bug can no longer reproduce it and indeed verify that the bug is now fixed, the loop has been truly closed.

This is why Applause supports an end-to-end bug fix verification (BFV) process. After an organization has fixed a bug that was identified by Applause’s curated team of vetted QA testers, the bug can be sent back to the Applause community and re-tested.

Benefits of Running BFV with Applause

Here are a few benefits of running a BFV process with Applause:

  • Peace of mind that bugs are fixed before they are pushed to the field
  • Third-party verification takes the process out of the hands of engineers or test labs, where verification might be difficult
  • Automated process with two-way integration enables a continuous integration workflow
  • Empowers a real-time Applause Quality Score™ rating

Let’s dig into these in a little more detail. First off, if the purpose of QA is to prevent show-stopper bugs from reaching your customers, then your last line of defense shouldn’t be fixing a bug — it should be confirming that the bug can’t be reproduced. A trained QA team that knows how to reproduce bugs is the best way to confirm that the bug won’t impact your customers.

That leads into the next point — engineers are not always equipped to reproduce bugs, and therefore can’t say with certainty that the bug is actually fixed. The engineer could run an automation regression test, sure — but remember, QA professionals bring a unique skill set, and it’s not realistic to expect an engineer to fill those shoes. QA better understands how to reproduce the bug, and can test for it on multiple devices and browsers.

Given the need for development velocity, Applause has automated and sped up the Bug Fix Verification process. As part of Applause’s two-way integration with organizations’ Jira bug tracking system — which you can read much more about here — Applause can automatically receive a notification of fixed bugs and reassign them back to testers that can verify the bug fix on the same environments (device, country, language, etc.) as the bug that was originally reported. These efficiencies are especially useful for CI teams, since BFV makes it easier to test more often and faster.

Applause can automatically receive a notification of fixed bugs and reassign them back to testers that can verify the bug fix on the same environments (device, country, language, etc.) as the bug that was originally reported

In addition, Applause now provides an Applause Quality Score rating, or AQS™ rating, as a way to quantify the quality of individual software builds. Using advanced algorithms, the AQS rating shows, on a scale of 0-100, the strength of a build. Applause’s BFV process ensures that number reflects the quality of the builds after the bug(s) have been addressed. Moreover, the updated bidirectional Jira integration not only streamlines the BFV process and the way the score is calculated, but also yields a much more accurate calculation, based on how an organization prioritizes issues in Jira.

Why Applause Should Help

Organizations often leverage their internal QA team to verify that the Engineering team has successfully addressed the bugs that Applause identified. This is a good best practice — if an organization’s internal QA team can still reproduce the bug, then it’s clear that the bug is still live and needs to go back again to Engineering.

The nature of Applause’s global community of trained QA testers often make this group the best candidate to verify that the bug no longer exists.

Applause’s testers are spread across the world, from North America to Africa to Asia and everywhere in-between. They are conducting in-market, localized and “in-the-wild” testing, which is impossible for an internal QA team to replicate, especially at scale and in the midst of a global pandemic, when it is outright impossible to match Applause’s global reach.

In addition, Applause can access hundreds of devices to test on and confirm the fix works across mobile, web and IoT devices. As an example of how this looks in practice, read up on how Applause recently provided testing across 98 iOS and 105 Android devices for Mobimeo.

Process with Applause Jira Integration

Our earlier blog post highlights how Applause offers integration capabilities with bug tracking systems, such as Jira, to speed up development velocity and reduce the need for manually moving bugs from the Applause Platform to an organization’s bug tracking system.

For organizations that leverage Jira, Applause offers a two-way integration that enables an automated and smooth Bug Fix Verification process. Here’s how the process works:

  1. 1. After the organization fixes a bug, the Applause team gets an automated message to retest the bug. Applause receives the issues based on how the organization prioritizes the bugs, ensuring that Applause reviews the most critical bugs first
  2. 2. The tester reads through the original bug that was logged, follows the same steps to attempt to reproduce the bug, and verifies if the bug was actually fixed or not
  3. 3. If the bug is fixed, the Applause team sends the bug back to the organization’s Jira as a verified fix
  4. 4. If the bug is not fixed, the Applause team bumps the bug back a stage so that the organization’s Engineering team can readdress it

Get Started with Applause’s Bug Fix Verification

Applause is ready to get started with verifying your bug fixes today.

If you’re a current customer and want to learn more about leveraging Applause for bug fix verification, reach out to your delivery manager for more information.

And if you’re just learning about Applause and want to know more about our fully managed service and capabilities to identify bugs, head here to reach out and we’ll be in touch soon.

The Tale of the Tape: Applause vs. Offshoring

The Tale of the Tape: Applause vs. Offshoring

Ebook

To succeed today, you must find the right QA partner. While you have your share of options, there is only one clear choice in the end. See how your options stack up against one another.

READ NOW

You might also be interested in: