Component testing best practices
nuxt4⚙️testing
Hi all,
So, we're adding testing to our nuxt-4 migration, and we're all relatively new to testing. Our application is a Nuxt-4 SPA. It uses Pinia stores and we use auto-imports.
Everything we migrate will need unit/component testing with a code coverage target. e2e is something we're not looking at right now though.
We're setting up component testing using
The guide says
If we're using auto-imports, wouldn't that mean all our components (and also stores) rely on the Nuxt runtime?
So, is it best practice that all component tests should run inside the Nuxt runtime using
This is just one of those things I just don't understand well enough, so any guidance on the intended testing philosophy here would be really appreciated
So, we're adding testing to our nuxt-4 migration, and we're all relatively new to testing. Our application is a Nuxt-4 SPA. It uses Pinia stores and we use auto-imports.
Everything we migrate will need unit/component testing with a code coverage target. e2e is something we're not looking at right now though.
We're setting up component testing using
@nuxt/test-utilsThe guide says
Using Vitest projects, you have fine-grained control over which tests run in which environment:
Unit tests: Place regular unit tests in test/unit/ - these run in a Node environment for speed
Nuxt tests: Place tests that rely on the Nuxt runtime environment in test/nuxt/ - these will run within a Nuxt runtime environment
If we're using auto-imports, wouldn't that mean all our components (and also stores) rely on the Nuxt runtime?
So, is it best practice that all component tests should run inside the Nuxt runtime using
@nuxt/test-utilsThis is just one of those things I just don't understand well enough, so any guidance on the intended testing philosophy here would be really appreciated
