Research indexJournal article
Ordering broken unit tests for focused debugging
Gälli, Lanza, Nierstrasz and 1 other
23 Dec 2004
NobleIDark:/48914/w1/20260516/0DC2A4FADOI10.1109/icsm.2004.1357796
Ordering broken unit tests for focused debugging
Gälli, Lanza, Nierstrasz and 1 other · 2004 · Subscription
NobleIDark:/48914/w1/20260516/0DC2A4FADOI10.1109/icsm.2004.1357796
The full text is at the publisher
You can read the abstract here, or open it at the publisher.
Abstract
Current unit test frameworks present broken unit tests in an arbitrary order, but developers want to focus on the most specific ones first. We have therefore inferred a partial order of unit tests corresponding to a coverage hierarchy of their sets of covered method signatures: When several unit tests in this coverage hierarchy break, we can guide the developer to the test calling the smallest number of methods. Our experiments with four case studies indicate that this partial order is semantically meaningful, since faults that cause a unit test to break generally cause less specific unit tests to break as well.