Skip to Main content Skip to Navigation

Rotten Green Tests A First Analysis

Abstract : Unit tests are a tenant of agile programming methodologies, and are widely used to improve code quality and prevent code regression. A passing (green) test is usually taken as a robust sign that the code under test is valid. However, we have noticed that some green tests contain assertions that are never executed; these tests pass not because they assert properties that are true, but because they assert nothing at all. We call such tests Rotten Green Tests. Rotten Green Tests represent a worst case: they report that the code under test is valid, but in fact do nothing to test that validity, beyond checking that the code does not crash. We describe an approach to identify rotten green tests by combining simple static and dynamic analyses. Our approach takes into account test helper methods, inherited helpers, and trait compositions, and has been implemented in a tool called DrTest. We have applied DrTest to several test suites in Pharo 7.0, and identified many rotten tests, including some that have been " sleeping " in Pharo for at least 5 years.
Document type :
Complete list of metadata

Cited literature [28 references]  Display  Hide  Download
Contributor : Lse Lse Connect in order to contact the contributor
Submitted on : Thursday, August 23, 2018 - 12:50:27 PM
Last modification on : Wednesday, March 23, 2022 - 3:51:22 PM
Long-term archiving on: : Saturday, November 24, 2018 - 2:00:23 PM


Files produced by the author(s)


  • HAL Id : hal-01819302, version 2


Julien Delplanque, Stéphane Ducasse, Andrew Black, Guillermo Polito. Rotten Green Tests A First Analysis. [Research Report] Inria Lille Nord Europe - Laboratoire CRIStAL - Université de Lille; Portland State University, Oregon, USA. 2018. ⟨hal-01819302v2⟩



Record views


Files downloads