Tom Mrazauskas

@Angel21PC Try creating two separate `jest.config` files for Vue Test Utils and for Nuxt Test Utils. They need different setup. Simply create config with just `preset: '@nuxt/test-utils'` and use it...

If your goal is end-to-end testing of an app using `playwright`, I would suggest using their own test runner instead of `jest`. Because: * it is faster * very similar...

Here is the promised config for Playwright Test Runner: ```ts // playwright.config.ts import { PlaywrightTestConfig } from '@playwright/test' const config: PlaywrightTestConfig = { webServer: { command: 'yarn build && yarn...

> I would appreciate any comments that shed some light on it. @Angel21PC It is complicated. See https://github.com/nuxt/test-utils/issues/275 for some hints on the root of this problem.

What about https://codspeed.io or https://bencher.dev? I like how Bencher is calling it continuous benchmarking.

> It's about iterating on the same function, not about catching regressions. Sort of comparing performance between two branches? Would that be possible without JSON being written to disk?

I was trying out `jest-light-runner` hoping for better performance, but it is visibly slower. In my case it was enough to run a single file with five test cases. A...

First of all, thank you for this library. After trying it out, I though it would work brilliantly as Jest environment. Happy to find this discussion. ## Working Prototype To...

Thanks for quick reply. I was not sure what should be the next step, but now everything got clear. I will work on the real implementation and will send a...

Sure. That’s exactly what I was thinking. Also I see how few small optimisations could be made in the core. Will send these in while working on the environment.