Conclusion

In this study, we presented an approach for tracing the effects of techniques for refactoring and aggressive unit testing in code. We examined 254 integration versions of a large Java framework. The integration versions stem from a continuous integration process that enables XP-like development of the framework.

We showed the usefulness of our approach and discussed how the effects of "test-infected development" can be seen in the history of specific system properties. In addition, we were able to highlight some areas for potential improvement in the development process.