Spend less time fixing bugs and more time writing code

Did you know that development teams spend 50% of their development time debugging?

As code becomes more complex, finding and fixing bugs is correspondingly harder, and traditional approaches to debugging are struggling to cope.

Debugging costs US $312 billion annually

The University of Cambridge found that debugging is costing the global economy at least $312 billion USD per annum. To put this into perspective, between 2008-2013, the Eurozone spent $591 billion on bailout payments to Greece, Ireland, Portugal and Spain; less than half the amount spent on software debugging over that same five-year period.

Debugging is getting harder

Brian Kernighan famously said “Everyone knows that debugging is twice as hard as writing a program in the first place. So if you're as clever as you can be when you write it, how will you ever debug it?”. As the world becomes ever-more dependent on complex software and bugs become harder to fix, traditional techniques and debuggers are of limited value in helping developers find the root cause.

Software quality is suffering

Aviation, the financial services, and automotive are the most famous industries to have experienced catastrophic failures or production outages. With thousands more tests being run every hour, making triaging failures a nightmare for QA/Test teams, the potential for bugs to make it into production is higher, the results of which can be catastrophic for your business.

faster debugging

The result

Financial and reputational costs

Failure to find and fix bugs quickly has a financial, personal and reputational cost to an organization. Products ship late (or not at all) while production failures can seriously damage a company’s reputation.

Drain on productivity

If 50% of your team’s development time is taken up by debugging, this is 50% of time not spent writing new code or bringing new products to market.

Catastrophic failures

A single production outage could spell the end of your business, forcing you to fix each and every test failure, or use the most expensive resources at your disposal to fix problems in your production software.

We've got the solution

Undo’s suite of innovative products are designed for developers working in QA/Test and on production software. Record all or part of your program’s execution, and use our interactive reversible debugger to fix bugs in minutes, not weeks.

  • Save money

    Reversible debuggers significantly improve development productivity, saving software vendors $81.1 billion USD per annum.

  • 26% faster debugging

    The University of Cambridge found that Undo’s reversible debugging technology reduces time spent debugging by at least 26%. Find and fix errors quickly and free up resource to work on more productive things, such as writing new code

  • Improved quality

    See any value in your program's memory or registers for any instruction in its execution history. Have a precise understanding of your software, whether in test or in production.

Undo products

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

What is reversible debugging?

Everything you need to know about reversible debugging and why you should use it.

Read whitepaper
Top