Did you know that you can set a starting point for ATC and, thanks to that, be able to run ATC in legacy code?

For years, I have been advocating that ABAP Test Cockpit should always be run on all developed code. This is easy to do with new code. But what about changes made to old, inherited code with thousands of lines full of errors?

In this case, you can use an ATC feature called Baseline. This feature allows you to add results from an ‘ATC run’ to the baseline so that, in future ATC runs, these results will be ignored, considered excluded, or set to low priority, as desired.

Run ATC on your legacy code and then add its billions of problems to the ATC Baseline. Once that is done, you can run ATC at will on legacy code and it will only report new problems that do not already exist in the baseline you have defined.

Greetings from Abapinho.