Diagnosing evolution in test-infected code

In this study we trace the effects of applying the techniques of refactoring and aggressive unit testing in source code based on historical information. We show how their impact on the evolution of the architecture can be testified. The study comprises the analysis of a large number of individual integration versions of a large framework. The method described here can help development teams find weaknesses in their application of the two traced techniques.

[1]  K. Beck,et al.  Extreme Programming Explained , 2002 .

[2]  Harald C. Gall,et al.  Software evolution observations based on product release history , 1997, 1997 Proceedings International Conference on Software Maintenance.

[3]  Mikael Lindvall,et al.  How well do experienced software developers predict software change? , 1998, J. Syst. Softw..

[4]  Heinz Züllighoven,et al.  JWAM and XP: using XP for framework development , 2001 .

[5]  Alistair Cockburn,et al.  Surviving object-oriented projects: a manager's guide , 1998 .

[6]  Martin Lippert,et al.  Stabilizing the XP Process Using Specialized Tools , 2001 .

[7]  Kent Beck,et al.  Test-infected: programmers love writing tests , 2000 .

[8]  Jan Bosch,et al.  Observations on the evolution of an industrial OO framework , 1999, Proceedings IEEE International Conference on Software Maintenance - 1999 (ICSM'99). 'Software Maintenance for Business Change' (Cat. No.99CB36360).