It was necessary to exclude src/groovy/org/eso/phase3/rm/utils/DbHelper.groovy from Clover instrumentation. If this file is instrumented, tests using the DbHelper class fail with an error like this:
grails test-app -clover.on
Failure: | test change batch status for operator(org.eso.phase3.rm.TestBatchServiceIntegrationSpec) | java.lang.NoClassDefFoundError: Could not initialize class org.eso.phase3.rm.utils.DbHelper at java.lang.Class.forName(Class.java:348) at org.eso.phase3.rm.BatchService.$tt__changeBatchStatus(BatchService.groovy:525) at org.eso.phase3.rm.TestBatchServiceIntegrationSpec.test change batch status for operator_closure208(TestBatchServiceIntegrationSpec.groovy:2270) at org.eso.phase3.rm.TestBatchServiceIntegrationSpec.test change batch status for operator(TestBatchServiceIntegrationSpec.groovy:2269)
We are using clover 4.1.1
Grails version 2.5.3
can you help?
Please create a ticket on support.atlassian.com, attach source code of the DbHelper class as well as one test class using it. Please also run your build with debug logging and attach log produced.
I suspect that either tests are trying to load this DbHelper class in a specific way (for instance Clover's classes are missing in the test class path) or there was some bug during instrumentation (for instance groovyc produced invalid bytecode for DbHelper), but we need more data to investigate it.
Thanks in advance!
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot