Clément P.

> @clementprevot While this is being fixed, you could disable the `jest` plugin so that you can continue to get traces while avoiding the errors. You would be missing any...

> @clementprevot Both `tracer.init()` and `tracer.use()` should be called before `jest-environment-jsdom` is imported, otherwise it's too late to disable the plugin. Ah! Good to know! Let me try that. Thanks...

Well, you solved it. Even without disabling the `jest` plugin, it now works perfectly fine if I `init` the tracer before importing `jest-environment-jsdom`. Thanks a lot for you help again!

@rochdev I have a quick update on this: in my previous comment I said that it was working fine, but it occurs in the end that it's not exactly true....

Hi @juan-fernandez Thank you for your answer. I indeed moved the initialization of the tracer above the requiring of th the JSDOM env. It fixed most of the tests, but...

Updating everything to the same version number didn't changed the issue with some of the tests. I still have to disable the jest plugin

Nope the error is not the same as the one mentionned in the first message of this issue. And it's not the same error for all tests. At first, those...

Hi @juan-fernandez I can try this release. I'll let you know how it went! Thanks for letting me know!

@juan-fernandez Sorry about the delay, I had some health issues recently and haven't been often at work. Sadly, the 2.4.2 release didn't solved my problem and I still had soem...

OK, I tested with v2.7.0 and I still have some weird behaviour. Let's take this example: ``` const activeMarkets = [ markets[COUNTRIES.DE], markets[COUNTRIES.AT], markets[COUNTRIES.ES], ] it.each(activeMarkets)( 'shows the active markets...