JaCoCo is agnostic to the way you run your tests. If you can execute your tests without JaCoCo, then execution of tests with JaCoCo shouldn't differ.
Make sure that you generate reports on a correct stage, i.e. if your tests are execuetd as "integration tests" ( maven-failsafe-plugin or something like that ), then obviously report generation should be bound to the phase after it, e.g. "post-integration-test". Please understand that we can't provide super precise help on hundreds of third-party frameworks and examples of the hundreds of cases. Obviously configuration might require some tuning, it is a bit unfair to believe that someone is gonna do all the homework. On Wednesday, September 28, 2016 at 5:18:08 PM UTC+2, [email protected] wrote: > > Hi, > > Thanks a lot for the quick reply. From the information you have provided I > could create a sample multi-module project and was successfully able to > replicate the same thing I was asking in the above request. But that was > all using unit tests only. > > Majority of the test cases we use are Spring tests (meaning they use > @ContextConfiguration annotation) written for Controllers using testNG > framework. When I run the build I see that this configuration is running > only unit tests with @Test annotation. Spring tests which are triggered > from testNG suite.xml file are not running. I have many such xml files > which trigger the testControllers and test end-to-end functionality. > > Please help me with the same on how to run these integration spring tests > with jacoco. > > Thanks > Yashwanth > > -- You received this message because you are subscribed to the Google Groups "JaCoCo and EclEmma Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/c5db4872-7947-4c6e-9809-a883914a10ec%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
