checkScoverage is checking line coverage, not statement coverage #38
Comments
|
Yes, this is based on the old SCCT output which was in the cobertura format. I think I prefer reading from the scoverage xml file, rather than using the Scala API? |
|
It's ok. I'll implement this one and create a PR. |
Kwestor
added a commit
to Kwestor/gradle-scoverage
that referenced
this issue
Feb 10, 2015
`checkScoverage` task now can check statement, branch or line coverage.
Default behavior is to check if statement coverage is >= 75%.
To change it, add:
```
checkScoverage {
coverageType = <type>
}
```
where `<type>` can be `'Line'`, `'Branch'` or `'Statment'`.
Fixes scoverage#38
Kwestor
added a commit
to Kwestor/gradle-scoverage
that referenced
this issue
Feb 10, 2015
`checkScoverage` task now can check statement, branch or line coverage.
Default behavior is to check if statement coverage is >= 75%.
To change it, add:
```
checkScoverage {
coverageType = <type>
}
```
where `<type>` can be `'Line'`, `'Branch'` or `'Statment'`.
New feature comes with bunch of tests for all scenarios.
Fixes scoverage#38
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As in summary. Main idea of scoverage is to calculate statement coverage, as line coverage in Scala is not a reliable statistics.
I understand existing clients depends on current behavior, but I think gradle plugin should at least provide ability to change this behavior.
We can either read
statement-rate="0.00" branch-rate="0.00"fromscoverage.xmlfile, or run testCoverage task and read it from there (like sbt plugin).The text was updated successfully, but these errors were encountered: