CODEWITHSUNDEEP
mavenjacoco
luharb87
luharb87

Reputation: 15

Running jacoco report where integration tests are in one code base and source code is in another code base

I recently started working on creating jacoco reports for maven projects including unit and integration tests and they seem to work out correctly. Now I have encountered a different scenario which I am not sure how to approach. I have one workspace which consists of integration test cases - application A, but the source code does not exist in the same workspace/code base. The source code which actually runs on invoking these integration test scripts are in a different workspace/code base - application B(they are invoked using rest api calls with the localhost urls. The jboss server is started for application B so that the localhost context is up) from the integration tests. The aim is to invoke these integration tests from application A, which in turn calls the source code of these tests in application B generating the jacoco report of the code coverage for application B. I am not actually sure how to achieve this. Can someone provide some input.

Thanks.

Upvotes: 1

Views: 639

Answers (1)

Mark Bramnik
Mark Bramnik

Reputation: 42461

If I understand you correctly, you actually have 2 different processes in your scenario:

  • The "client" process that runs the integration tests and for which jacoco can be easily applied, but it's not what you need

  • The "server" process that runs the actual JBoss server and executes the actual code.

Client process contacts the server via HTTP.

In this case, I'm afraid jacoco won't be able to provide a coverage for you if you're running the tests from maven/gradle, because jacoco instruments only bytecode on the running JVM. So you have to be "creative" here :)

I'll list here some possible approaches Disclaimer: I haven't tried them though (didn't work with jboss/java ee), but maybe you'll be able to at least borrow some ideas

The first approach would be running the tests together with the application somehow, like its done for example in spring tests (I'm not sure whether JBoss provides similar capabilities).

The idea is simple:

  • You run the integration test, it runs the jboss "embedded in the same jvm" and you can inject beans / EJB session beans into the test (like autowiring with spring).

The advantage of such a method is that you'll be able just to use jacoco maven plugin and it will instrument everything for you

I don't know how easy will be achieving this architecture technically, I know that recent jboss versions support embedded mode, So maybe you'll find This link to be a useful foundation

Another direction is to take a look at Arquillian project. They have some jacoco extension that probably will help, but I've never tried it.

And the last approach I can think of is running the jboss server with jacoco agent directly instead of relying on the build system that runs jacoco for you.

The idea here is to stream the results of covered server code into some file / tcp endpoint. So you run the jboss with -javaagent:[yourpath/]jacocoagent.jar and it starts streaming the results wherever you need it to stream. After the tests you should gather these results and prepare a report. You can find Here more information about this approach

Upvotes: 1

Related Questions