White Papers

Presented at DVCon US 2016, Mar 2016, San Jose, CA.

How often should you launch your test suites in order to find bugs fast at little cost? What is the optimal launch schedule?

Download PDF

Presented at Microprocessor and SoC Test and Verification (MTV 2015), Dec 2015, Austin Texas.

Several EDA tools automate the debug process or part of the debug process. The result is less manual work and bugs are fixed faster. However, the actual process of fixing the bugs and committing the fixes to the revision control system is still a manual process. In this paper we explore how to automate that last step: automate bug fixing.

Download PDF

Presented at DVCon Feb 2015, San Jose, CA

A popular approach to regression testing is to test every commit to the revision control system with a short test suite. The idea is that if this short test suite fails then we know which commit that caused the problem and the committer can be automatically notified about his or her mistake.

Download PDF

Presented at the Microprocessor Test and Verification Conference (MTVCon13)

The purpose of regression testing is to quickly catch any deterioration in quality of a product under development. The more frequently tests are run, the earlier new issues can be detected resulting in a larger burden for the engineers who need to manually debug all test failures, many of which are failing due to the same underlying bug. However, there are software tools that automatically debug the test failures back to the faulty change and notifies the engineer who made this change. By analyzing data from a real commercial ASIC project we measured whether bugs are fixed faster when using automatic debug tools compared to manual debugging. We saw that bugs that had been automatically debugged was fixed 4 times faster.

Download PDF