Abstract Many software production processes advocate rigorous development testing alongside functional code writing, which implies that both test code and production code should co-evolve. To gain insight in the nature of this co-evolution, this paper proposes three views (realized by a tool called TeMo) that combine information from a software project's versioning system, the size of the various artifacts and the test coverage reports. We validate these views against two open source and one industrial software project and evaluate our results both with the help of log messages, code inspections and the original developers of the software system. With these views we could recognize different co-evolution scenarios (i.e., synchronous and phased) and make relevant observations for both developers as well as test engineers.
Zaidman et al. REF have examined the co-evolution of code and tests on two open-source and one industrial Java applications.
Studying the co-evolution of production and test code in open source and industrial developer test processes through repository mining
Empirical Software Engineering
Empirical Software Engineering
Engineering Computer Science