vite-jest VS c8

Even the most official workaround, vite-jest, still has issues to work through, like a lack of Windows support.

I had originally planned to keep using Jest during the migration of CRA to ViteJS, but I kept running into issues, mainly because Jest support for ES Modules is still experimental. There is a Vite plugin called vite-jest but it's still very much a work in progress.

Then I tried Vite. Vite also supports lots of things out of the box (especially ESM!). Its HMR - hot module replacement is blazing fast. I can also use plugin like vite-jest (switch to esbuild-jest later on) to replace Babel and speed up my tests. This is the first time I have a relatively "GOOD" DX.

🔍 c8 for code coverage

We use Mocha with Chai for tests - works perfectly. We use c8 for coverage, which is a drop-in replacement for nyc which doesn't (or didn't when we switch) support import. We then use husky for managing git hooks, such as ensuring all tests pass to allow a push (which can be forced through if needed).

coverage: This is the configuration I use for the c8 reporter. I also specify the folders that I exclude from the report.

We use c8c8 for generating test coverage and set a threshold of 70% coverage to pass our build.

Adding coverage report is easy by installing a package c8

Hello everyone, I'm using uvu for testing. And installed c8 for coverage. Yet it doesn't seem to be able to pick up test .svelte files. Does anyone knows how to achieve this or any other way of getting .svelte files coverage? Thanks

Are you using nyc (the Istanbul command line interface that reports the code covered by your tests)? It’s not ready for the future, yet. The good thing is that V8 (the JavaScript engine behind Node.js) has code coverage built-in. You can take advantage of it using c8. A CLI similar to nyc. And because it relies on the build-in V8 code coverage it always works with the newest syntax supported by Node.js.