On Sat, Feb 13, 2016 at 8:22 PM, Max Leske <maxleske@gmail.com> wrote:

How about enforcing coverage? I know that coverage tests don��t say anything about the quality of the test cases but it��s (almost) always better to have some tests than none. I wouldn��t set the bar too high either for coverage, maybe 60 or 70%. 100% is unrealistic, but 60 to 70 should be achievable with a couple of well written tests.

Of course we would need a way to run coverage tests on the test suite. Do we have a tool for coverage tests?

Yes, there's Hapao��http://objectprofile.com/Hapao.html

you can install it from Catalog Browser under the name "Spy2". (There's more to Spy2, but Hapao is included.)

So maybe CI could run the coverage and issue a warning if it is under a certain threshold, however the doesn't really cover adding new features (e.g. project has 80% coverage�� new untested features are added, coverage drops to 75% and nobody notices).

Peter