Generating Unit Tests with Descriptive Names Or: Would You Name Your Children Thing1 and Thing2?
The name of a unit test helps developers to understand the purpose and scenario of the test, and test names support developers when navigating amongst sets of unit tests. When unit tests are generated automatically, however, they tend to be given non-descriptive names such as “test0”, which provide none of the benefits a descriptive name can give a test. The underlying challenge is that automatically generated tests typically do not represent real scenarios and have no clear purpose other than covering code, which makes naming them di cult. In this paper, we present an automated approach which generates descriptive names for automatically generated unit tests by summarizing API-level coverage goals. The tests are optimized to be short, descriptive of the test, have a clear relation to the covered code under test, and allow developers to uniquely distinguish tests in a test suite. An empirical evaluation with 47 participants shows that developers agree with the synthesized names, and the synthesized names are equally descriptive as manually written names. Study participants were even more accurate and faster at matching code and tests with synthesized names compared to manually derived names.
Mon 10 JulDisplayed time zone: Tijuana, Baja California change
13:45 - 14:35
|Targeted Property-Based Testing|
|Generating Unit Tests with Descriptive Names Or: Would You Name Your Children Thing1 and Thing2?|
Ermira Daka University of Sheffield, UK, José Miguel Rojas University of Sheffield, Gordon Fraser University of SheffieldDOI