Closed ksoichiro closed 10 years ago
Thank you very much for this!
I don’t know why Covertura judges that some codes are not covered. I think they are actually tested.
I agree on this. Cobertura seems to have problems on these lines. It started when we started using version 2.0 of gradle, by the way (#21). There wasn't this problem with gradle 1.x...
Thanks!
There wasn't this problem with gradle 1.x...
Gradle 1.x is based on groovy 1.8 and gradle 2.0 is based on groovy 2.3. http://forums.gradle.org/gradle/topics/gradle_2_0_released Maybe there are some significant changes in groovy 2.x..
Anyway, thanks for merging!
Added test codes for detecting Android Plugins (which I wrote in #25).
Android plugin checks Gradle version in
BasePlugin#apply()
and if it’s not applied on supported versions,BuildException
will be thrown.gradle-android-plugin
apply()
< v0.12
>= v0.13
So I wrote some fake plugins just for testing the target codes.
If
coveralls-gradle-plugin
supports Gradle 2.1 in the future, these test codes should be replaced.Sorry for dropping the coverage eventually but I don’t know why Covertura judges that some codes are not covered. I think they are actually tested. (I mean,
c.name == name || instanceofWithName(c.superclass, name)
inJacocoSourceReportFactory#createTargetSrcDirs()
)Thanks!