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
> On 5. Mar 2025, at 04:08, Rajeev Nandan wrote:
>
> Hi M
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.
On Wed, 5 Mar, 2025, 12:21 am Marc Hoffmann,
wrote:
> Hi Prabitha,
>
> execution data is written in a global, shared store. If you run mult
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
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 y
