Open chucklever opened 4 months ago
We are building quite a menagerie of tests, but we still don't know where the untested code paths are. It would be nice to build some tooling (or best practices) for generating code coverage data while running our CI/QA tests.
We are building quite a menagerie of tests, but we still don't know where the untested code paths are. It would be nice to build some tooling (or best practices) for generating code coverage data while running our CI/QA tests.