Code coverage patch results are wrong with subprojects

When creating pull requests, apparently random changes to coverage are reported. For example, for a commit with just changes to three lines of code, we get a decrease in coverage by 22%

My hunch is that our coverage is reported in this project from 4 different subproject: junits, integration tests, karate API tests and Jest client tests. But not all those tests run if that subproject isn’t touched since the builds are fairly expensive. Codecov doesn’t hang onto the previous tagged coverage however.

@ari, are you looking for something like carryforward flags?

@tom Thanks, that looks like it might do the job. I’ll need to spend some time to understand how to integrate those with our github action test runs.

1 Like