We have some support in our gradle build to run tests coverage manually with something like this:
../gradlew clean test integrationTest distributedTest acceptanceTest -PcodeCoverage jacocoOverallTestReport This should generate a code coverage report. At one point I know we were talking about integrating with analysis.apache.org, which is running sonarqube, but I don't know what happened with that. I don't think there is any job that is automatically running these tests with coverage. -Dan On Fri, Nov 10, 2017 at 12:11 PM, Patrick Rhomberg <prhomb...@pivotal.io> wrote: > Hello, all. > > While looking at expanding testing coverage, the natural question arose: > what does the existing test coverage map look like? > Does anyone know if we have an existing code-coverage analysis done as > part of our testing? If there is, does anyone know if our DUnitTests or > AcceptanceTests are (or could be) included in the coverage map? I think > this could be a very useful tool in driving new tests and the detection of > dead code. > > Imagination is Change. > ~Patrick >
