Simen Bekkhus
Simen Bekkhus
Perfect, thanks @nicolo-ribaudo! I'll try to find the time soonish to dig into this
The test will fail regardless (or rather, the snapshot will then encode a failing test as correct, which it's not 🙂 )
FWIW, I believe the underlying issue here is one of the ones tracked in https://github.com/nodejs/node/issues/37648 (specifically the shared cache thing), so I'm waiting for that to be resolved upstream before...
Mind signing the CLA?
>@SimenB has there been any discussion on the default testEnvironment? Yes, #5815. If you use `jest --init`, it defaults to `node` as well. I'd forgotten #5815 was accepted, would be...
>Because this first run is not inBand, the overhead causes it to take about 2.2s on my device (even without JSDOM) Can you test with node worker threads? Still some...
Workers are always reused, do you mean the sandbox? If so, no - we want every test to run in isolation However, we want to lift jasmine/circus out of the...
That should be fixed - the worker pool should be reused. Could you bisect?
>I've determined the culprit to be `micromatch@3` Really? Interesting! Looking forward to the analysis 🙂
Seeing as it's a major, we'll probably upgrade in Jest 25 to be on the safe side