Fix failing tests and improve software quality

What to do with all those test failures?

It’s become standard practice to perform rigorous testing but with 1000s more tests being conducted every hour, even a 0.1% failure rate can pose a nightmare for triaging.

Fixing tests takes too much time

Automated tests, or more recently, continuous integration and continuous deployment, tend to reveal code problems earlier than the more traditional weekly test runs or ad-hoc testing. However, these practices don’t help you with diagnosing the cause of test failures, which is what takes up a large proportion of developers’ time.

A growing backlog of failing tests

As your codebase grows, it is harder to fix each and every test failure, especially those which fail intermittently or don’t always fail in the same way.  Often we don't have the time or ability to isolate and diagnose these types of failures, putting them at the back of the queue and helping to create a backlog of tests that are ‘known’ to fail.

Barriers to collaboration

Developers can’t work on a problem until they can reproduce it, causing major difficulties for teams that have separate QA and Development departments. Sometimes failures that appear in QA  will not reproduce when examined by Development, creating an inability to collaborate and bad relations between teams.

Failed test backlog

The result

Ineffective and expensive

The University of Cambridge found that debugging eats up 50% of development time. That’s 50% of your expensive developers’ time spent fixing errors in your product rather than writing new code.

A production failure waiting to happen

A failing test demonstrates a risk that your product will fail in production - which can be catastrophic if the failure causes an outage or, worse, a security breach. Without diagnosing each and every test failure, you don’t know which failure is the dangerous one, so you must fix all of them to be certain, wasting time and resource.

We've got the solution

Undo’s Live Recorder for Automated Test automatically captures your test failure and everything about its execution as the failure happens, allowing you to identify, diagnose and respond to each and every failure that appears in your test suite.

  • Make triaging easier

    Failed tests now come as a recording, allowing developers to see exactly how the test failed.

  • Fix every intermittent failure

    Test failures are now 100% reproducible, allowing your developers to fix defects that would otherwise be impractical to address.

  • Enhanced collaboration

    Share recordings of failed tests between QA and Development, allowing them to see the exact set of circumstances that caused a test to fail.

Live Recorder for Automated Test

Useful related resources

Fuzz testing of SAP HANA using LRT

Learn how SAP is improving software quality in multi-threaded database, SAP HANA.

Download case study

Getting the most out of QA

See how Live Recorder helps you fix even intermittent test failures

Read whitepaper

Why you should adopt automated testing

Testing services are rarely part of broader strategic IT discussions. This is a mistake. Find out why.

Read article