Philosophy of @nuxt/test-utils

[gcugnet]

Hey!

I’m wondering what is the philosophy of @nuxt/test-utils library for the future.

I’m developping Vue applications, and I’m using Nuxt for several features (mainly plugins and middlewares).

I’ve recently dig the testing approaches and libraries for a Vue and Nuxt application.

It appeared that:

• Vue team advices to use Vitest:

Since the official setup created by create-vue is based on Vite, we recommend using a unit testing framework that can leverage the same configuration and transform pipeline directly from Vite. Vitest is a unit testing framework designed specifically for this purpose, created and maintained by Vue / Vite team members. It integrates with Vite-based projects with minimal effort, and is blazing fast.

Then, you can use specific libraries, such as @vue/test-utils to mount components in the testing environment, and Playwright for E2E testing.

• Nuxt team proposes @nuxt/test-utils with several additional functions (I’m mostly using the mountSuspended() and registerEndpoint() for now), to use with Vitest:

We currently ship an environment for unit testing code that needs a Nuxt runtime environment. It currently only has support for vitest (although contribution to add other runtimes would be welcome).

So I understood that @nuxt/test-utils is in a way built on top of Vitest, or at least that it needs it to be functional. I guess there is a lot of work to be done to create such a library and make it compatible with features from another library, and I really thank the team working on it. I have a question though: What is @nuxt/test-utils philosophy for time to come?

I’ve recently rode in @nuxt/test-utils v3.16.0 release changelog that the next major (realease) will:

drop support for vitest < 3

For me it seems like contradictory information, and I need to understand better how both Vitest and @nuxt/test-utils aim to evolve in the future: side by side or separately. I need to understand it better to make long term choices on my current projects, and maybe share my knowledge on it with other devs I can work with.

Maybe there are already information on it somewhere else (that I’ve haven’t found)?

Thank you for you reading time, and for your help and clarifications :)

[TheAlexLichter]

The line from the changelog simply means that Vitest major versions 1 and 2 are not supported, but Vitest 3 is and will be.

@nuxt/test-utils is working well with Vitest and is commonly used with the popular test runner but also is supporting jest or cucumber (source), as well as Playwright for E2e ☺️

[gcugnet]

Thank you for this clarification @TheAlexLichter 😄