Show simple item record

dc.contributor.authorBavota, G
dc.contributor.authorQusef, A
dc.contributor.authorOliveto, R
dc.contributor.authorBinkley, D
dc.contributor.authorDe Lucia, A
dc.date.accessioned2015-06-11T14:49:50Z
dc.date.available2015-06-11T14:49:50Z
dc.date.issued2014
dc.identifier.issn1382-3256
dc.identifier.urihttp://dx.doi.org/10.1007/s10664-014-9313-0
dc.identifier.urihttp://hdl.handle.net/10863/508
dc.description.abstractBad code smells have been defined as indicators of potential problems in source code. Techniques to identify and mitigate bad code smells have been proposed and studied. Recently bad test code smells (test smells for short) have been put forward as a kind of bad code smell specific to tests such a unit tests. What has been missing is empirical investigation into the prevalence and impact of bad test code smells. Two studies aimed at providing this missing empirical data are presented. The first study finds that there is a high diffusion of test smells in both open source and industrial software systems with 86 % of JUnit tests exhibiting at least one test smell and six tests having six distinct test smells. The second study provides evidence that test smells have a strong negative impact on program comprehension and maintenance. Highlights from this second study include the finding that comprehension is 30 % better in the absence of test smells.en_US
dc.publisherSpringer Verlag (Germany)en_US
dc.titleAre Test Smells Really Harmful? An Empirical Studyen_US
dc.typeArticleen_US
dc.date.updated2015-03-30T12:27:58Z
dc.language.isiEN-GB
dc.journal.titleEmpirical Software Engineering
dc.description.fulltextnoneen_US


Files in this item

FilesSizeFormatView

There are no files associated with this item.

This item appears in the following Collection(s)

Show simple item record