Results from introducing component-level test automation and Test-Driven Development

Author(s): L. Damm and L. Lundberg
Venue: J. Systems and Software
Date: 2006


Quality
3

Methodology: TDD
Duration: 1 to 1.5 years
Company: Ericsson AB
Type of project: Mobile devices
# of developers: About 50
project life: Legacy
Language: C++ and Java
Code Size (KLOC) New; Base; Total: Na, 70, na

This study had four concurrent products that were using TDD and did comparisons between those two. The evaluation methods used to compare between the two projects where investment cost, FST, AFC, Improvement rate, ROI (project view) and ROI (total) . The result of this was that the implementation of the new concept had significant improvement rates in form of decreased FST rates (5-30% improvement) and decreased fault costs, i.e. The Avoidable Fault Cost (AFC) was on average about 60% less than before. In practice, the result of the total fault cost became about 30% less. The validity of the results can be considered strong because all project comparisons showed similar improvement rates.

0