Open bdbogjoe opened 6 years ago
Thanks for the sample. I will take a look over the weekend if time permits.
It appears you were trying too hard to get things working and had more configuration than was needed.
Eliminating the additionalTestSourceSet configuration block completely makes the integration tests run and pass. The coverage for the application code appears correct.
This was the clover
configuration that worked:
clover {
report {
html = true
}
}
However, I see that there is a problem with this particular use case, Clover report does not include the Test Code report or any test results. I think that is a defect that has been there all along when additional Test tasks and test source sets are involved.
The plugin will automatically do the right thing for additional Test tasks in the build without any extra configuration. The additionalTestSourceSet is used when there is no direct correlation to the Test task and the source sets that must be recompiled with instrumentation. In this case you have an existing one-to-one mapping for Test task to source sets.
I will look into the reporting issues separately, I think the test execution issue was the result of setting the configuration when there was no additional sources to handle.
ok understand, issue is with report, thanks
I created sample repo to illustrate the issue :
https://github.com/bdbogjoe/grails-clover-integrationTest
just run grails test-app and you will get exception :