Create a Safety Net for Your Automated Tests
Remember how we monitored structural decay back in Use a Storyboard to Track Evolution? We’re going to set up a similar safety net for automated tests.
Our safety net is based on the change ratio between the application code and the test code. We get that metric from an analysis of change frequencies, just like the analyses you did back in Part I.
Monitor Tests in Every Iteration
To make it into a trend analysis, we need to define our sampling intervals. I recommend that you obtain a sample point in each iteration or at least once a month. In case you’re entering an intense period of development (for example, around deadlines—they do bring out the worst in people), perform the analysis more frequently. ...
Get Your Code as a Crime Scene now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
