Why do errors occur when using '@nuxt/test-utils/e2e' for API testing?
bugvitest-environment
#1 — nuxt e2e testing challenges cluster
Components tests it is triggering global route middleware
vitest-environment
#2 — monorepo test challenges cluster
Fail to mock a Nested Component with mockComponent
pending triage
Fixture timeout exceeded with Playwright test runner
bugpending triage
#3 — Unnamed cluster cluster
#4 — nuxt test environment optimization cluster
Ability to avoid a new nuxt instance for each test file
enhancementpending triage
Tests running in a GH action sharing a nuxt server a bit faster
vitest-environmentpending triage
#5 — mocking nuxt imports challenges cluster
Expose mocks directly with `mockNuxtImport`
enhancementgood first issuevitest-environment
mocking plugins used within nuxt
documentationenhancementvitest-environment
How to mock custom imports while using mountSuspended to test
bugvitest-environmentpending triage
mockNuxtImport doesn't work for nested composables
pending triage
#6 — nuxt test utils conflicts cluster
App.vue doesnt mount when running tests
enhancementpending triage
#7 — nuxt test utils vitest conflicts cluster
#8 — nuxt vitest coverage issues cluster
Support Vitest `projects` option for Browser Mode
pending triage