Sciweavers

KBSE
2009
IEEE

ReAssert: Suggesting Repairs for Broken Unit Tests

14 years 6 months ago
ReAssert: Suggesting Repairs for Broken Unit Tests
—Developers often change software in ways that cause tests to fail. When this occurs, developers must determine whether failures are caused by errors in the code under test or in the test code itself. In the latter case, developers must repair failing tests or remove them from the test suite. Reparing tests is time consuming but beneficial, since removing tests reduces a test suite’s ability to detect regressions. Fortunately, simple program transformations can repair many failing tests automatically. We present ReAssert, a novel technique and tool that suggests repairs to failing tests’ code which cause the tests to pass. Examples include replacing literal values in tests, changing assertion methods, or replacing one assertion with several. If the developer chooses to apply the repairs, ReAssert modifies the code automatically. Our experiments show that ReAssert can repair many common test failures and that its suggested repairs correspond to developers’ expectations.
Brett Daniel, Vilas Jagannath, Danny Dig, Darko Ma
Added 21 May 2010
Updated 21 May 2010
Type Conference
Year 2009
Where KBSE
Authors Brett Daniel, Vilas Jagannath, Danny Dig, Darko Marinov
Comments (0)