Thanks for the additional information. With this, I will address your original questions.
Eliminate the code coverage stats banner
You do this by disabling code coverage. How you accomplish this depends on what runner you are using and how the code is written. The out-of-the-box runner.cfm that comes with a ColdBox app for example, will usually just allow you to set
url.codeCoverageEnabled to false. However, if you have written your own runner which does not include the HTMLRunner.cfm from the core of TestBox, you may need to manually set the options when you create TestBox. We’d need to see more code to determine how your runner is working.
But I think that this just prevents it from performing code coverage and has no effect on the Code Coverage stats banner at the top of the page.
This is incorrect. If you see the banner, that means code coverage ran. It sounds like your attempts to disable the code coverage feature are not working which would require the information I discussed in the previous paragraph.
Generating these stats takes longer than executing all of my test.
Yes, for a large number of files, it can be slow. This is mostly due to the CF engine compiling all the files. Unless your app actually has 5,500 CF files, you can use the
coverageBlacklist feature to exclude directories that you do not want to be processed. Enabling the
coverageBrowserOutputDir setting will allow you to see a report of all the files being processed by code coverage.
What is the trigger for this banner and is there an option to not generate/calculate this banner?
Alternatively how do I clear/zero out these stats?
I don’t quite understand this question. The code coverage stats are recalculated on every test run. There’s no need for you to try and affect the stats yourself. They are simply a product of what code coverage is detected in your files.