-
- [ ] measure test coverage
- [ ] break build on less than 100%
Take the JaCoCo configuration from the *Komunumo* project:
https://github.com/McPringle/komunumo/
-
The value outputted by the action for `steps.jacoco.outputs.coverage-changed-files` is different from the value mentioned in the comment.
Here is an example comment from my repository:
### Code Cove…
-
-
### What happened?
I am getting the follow problem on my agent:
```
##[error]Failed to get FF TestManagement.Server.EnablePublishToTcmServiceDirectlyFromTask Value.
##[error]Failed to upload…
-
### New issue checklist
- [X] I searched for [existing GitHub issues](https://github.com/microsoft/azure-pipelines-tasks/issues)
- [X] I read [pipeline troubleshooting guide](https://docs.microsoft.c…
-
-
In project with more than one test file binary report (jacoco.exec) needed for jenkins or Sonar coverage is much smaller than XML or HTML report.
-
JaCoCo is the code coverage tool that atomashpolskiy/bt uses for its tests. This is what we should use when doing code coverage.
-
This works not out of the box but workaround can be found at
https://code.google.com/p/android/issues/detail?id=144664
-
We would like to get code coverage reports for our robolectric tests. The code coverage tool needs to be compatible with Kotlin and java, as well as work on Gradle and Bazel.
Jacoco seems to be a goo…