Reg: Capturing method data for cases run parallelly

[Prabitha Susil]

Hi Team,

 

I am using jacoco for capturing the class and method level data that is being touched by my test case. I am currently doing this by serially running one case after other to capture the data. This is intern taking a lot of time.

Is it possible to run scripts / test cases parallelly capturing the data touched by each case separately.

Thanks,

Prabitha

[Marc Hoffmann]

Hi Prabitha,

execution data is written in a global, shared store. If you run multiple test cases within the same JVM in parallel we cannot keep execution information apart.

The only option I see is to parallelize your tests in multiple JVMs.

Out of curiosity: Can you please share a bit about your use case? How are you processing and using the per-test coverage data?

Cheers,

-marc

--
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 jacoco+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/jacoco/CAMf5NwT%3DkQFOzHj%2BObQa-uKfUHcWBhLuxPh-8tMv4MMzkoGLoQ%40mail.gmail.com.

[Rajeev Nandan]

Hi Marc, 

I had the same use case where i wanted to capture code coverage for each test case separately.

Our use case was to find duplicate tests in a service under test. Here a test case means one api call or kafka consumption to the service under test. 

We wrote a java agent which identifies end of a test case abd then export the coverage data to an exec file. But this approach works only if we are running test cases one by one.

Can we tweak usage of session id and use it as test case id to store coverage data separately?

Thanks and regards,

Rajeev Nandan

To view this discussion visit https://groups.google.com/d/msgid/jacoco/C2B6D986-C5EF-4B87-83D3-426619C7845D%40mountainminds.com.

[Prabitha Susil]

Thanks Marc for that confirmation. We use this data to run only test cases that would be impacted due to a particular transaction change on the application.

To view this discussion visit https://groups.google.com/d/msgid/jacoco/C2B6D986-C5EF-4B87-83D3-426619C7845D%40mountainminds.com.

[Marc Hoffmann]

Hi Rajeev,

it is not about the session id. It is about the execution data storage: JaCoCo probes are stored in static fields. We cannot distinguish between concurrent test runs as we don’t have separate storage for them.

Regard,

-marc

To view this discussion visit https://groups.google.com/d/msgid/jacoco/CACQZ1%3DEZLceqJZ29RLRFTUs3yGgT99mxsP4qBTThssUuH852qA%40mail.gmail.com.