Why do errors occur when using '@nuxt/test-utils/e2e' for API testing?nuxt/test-utils · updated2 years ago · 77% similar bugvitest-environment
[test-utils] testing for prerender buildnuxt/test-utils · updated2 years ago · 75% similar enhancement
@nuxt/test-utils -- setup() clobbers console.log() functionalitynuxt/test-utils · updated2 years ago · 74% similar bug
Components tests it is triggering global route middlewarenuxt/test-utils · updated2 months ago · 74% similar vitest-environment
Vitest workspaces in a monorepo doesn't work.nuxt/test-utils · updated5 months ago · 78% similar pending triage
The "setup" in the tests is very slow for every rerunnuxt/test-utils · updated5 months ago · 75% similar enhancement
Intermittent "#imports" package specifier error in Nuxt environment tests (monorepo/layer setup)nuxt/test-utils · updated2 months ago · 75% similar pending triage
Fail to mock a Nested Component with mockComponentnuxt/test-utils · updated2 years ago · 71% similar pending triage
Fixture timeout exceeded with Playwright test runnernuxt/test-utils · updated2 years ago · 71% similar bugpending triage
Overriding global $fetch with `ofetch.create` will break the test runnuxt/test-utils · updated5 months ago · 79% similar pending triage
Overriding msw mock handler does not work when using `nuxt` environmentnuxt/test-utils · updated9 months ago · 79% similar pending triage
Ability to avoid a new nuxt instance for each test filenuxt/test-utils · updated2 years ago · 75% similar enhancementpending triage
Tests running in a GH action sharing a nuxt server a bit fasternuxt/test-utils · updated1 year ago · 73% similar vitest-environmentpending triage
Using the server from multiple test files does multiple unneccessary build runsnuxt/test-utils · updated1 year ago · 71% similar enhancementv0
Ability to `setup()` a server-only environment for testingnuxt/test-utils · updated1 year ago · 71% similar enhancement
Expose mocks directly with `mockNuxtImport`nuxt/test-utils · updated2 years ago · 78% similar enhancementgood first issuevitest-environment
mocking plugins used within nuxtnuxt/test-utils · updated10 months ago · 78% similar documentationenhancementvitest-environment
How to mock custom imports while using mountSuspended to testnuxt/test-utils · updated2 years ago · 78% similar bugvitest-environmentpending triage
`mockNuxtImport` for `@nuxt/test-utils/e2e`nuxt/test-utils · updated4 months ago · 78% similar pending triage
mockNuxtImport doesn't work for nested composablesnuxt/test-utils · updated7 months ago · 77% similar pending triage
Nuxt 4 + Layers breaks Nuxt Test Utilsnuxt/test-utils · updated10 months ago · 79% similar pending triage
Nuxt `multiApp` breaks nuxt/test-utilsnuxt/test-utils · updated4 months ago · 79% similar pending triage
App.vue doesnt mount when running testsnuxt/test-utils · updated1 year ago · 75% similar enhancementpending triage
Import of postgres ("pg") breaks when using nuxt test-utils in combination with vitest >= 4.1.0nuxt/test-utils · updated10 days ago · 75% similar pending triage
Following documentation and using `defineVitestConfig` results in an `[ERROR] "@nuxt/test-utils/config" resolved to an ESM file.`nuxt/test-utils · updated2 years ago · 81% similar documentationgood first issue
[nuxt] instance is not available in server utils unit tests with useRuntimeConfig()nuxt/test-utils · updated2 years ago · 80% similar bugpending triage
Error: This module cannot be imported in the Vue part of your appnuxt/test-utils · updated3 months ago · 79% similar pending triage
Unable to use vitest spy within nuxt 3 component methods.nuxt/test-utils · updated2 years ago · 79% similar pending triage
Error when loading browser-entry.mjs: Syntax error, "qs" does not provide an export named "default"nuxt/test-utils · updated8 months ago · 79% similar pending triage
pages are not covered in nuxt environmentnuxt/test-utils · updated3 months ago · 82% similar pending triage
Support Vitest `projects` option for Browser Modenuxt/test-utils · updated10 months ago · 79% similar pending triage
Reporter are not taken into account and it always use default reporternuxt/test-utils · updated28 days ago · 79% similar pending triage
Problem with nuxt imports: Vitest Coverage stays at 100% for components regardless of the existence of any component test because of nuxt importsnuxt/test-utils · updated8 months ago · 78% similar bugvitest-environmentpending triage
`@vitest-environment-options` is not workingnuxt/test-utils · updated3 months ago · 78% similar pending triage