Genova, Italy Italy
Mar. 5, 2013 to Mar. 8, 2013
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/CSMR.2013.26
Antipatterns are known as recurring, poor design choices, recent and past studies indicated that they negatively affect software systems in terms of understand ability and maintainability, also increasing change-and defect-proneness. For this reason, refactoring actions are often suggested. In this paper, we investigate a different side-effect of antipatterns, which is their effect on testability and on testing cost in particular. We consider as (upper bound) indicator of testing cost the number of test cases that satisfy the minimal data member usage matrix (MaDUM) criterion proposed by Bashir and Goel. A study-carried out on four Java programs, Ant 1.8.3, ArgoUML 0.20, Check Style 4.0, and JFreeChart 1.0.13-supports the evidence that, on the one hand, antipatterns unit testing requires, on average, a number of test cases substantially higher than unit testing for non-antipattern classes. On the other hand, antipattern classes must be carefully tested because they are more defect-prone than other classes. Finally, we illustrate how specific refactoring actions-applied to classes participating in antipatterns-could reduce testing cost.
Refactoring, Antipatterns, Object oriented testing, Testing cost
Aminata Sabane, Massimiliano Di Penta, Giuliano Antoniol, Yann-Gael Gueheneuc, "A Study on the Relation between Antipatterns and the Cost of Class Unit Testing", CSMR, 2013, 2011 15th European Conference on Software Maintenance and Reengineering, 2011 15th European Conference on Software Maintenance and Reengineering 2013, pp. 167-176, doi:10.1109/CSMR.2013.26