We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Isolated reproduction:
https://stackblitz.com/edit/nuxt-starter-xti8mf?file=app.vue,package.json,app.spec.ts,components%2FFetching.spec.ts,components%2FFetching.vue,nuxt.config.ts
run yarn vitest to see a failed spec that imo shouldve succeed
yarn vitest
When using registerEndpoint to mock an api response I'd expect to be able to validate the correct dom is displayed based on the mock response.
registerEndpoint
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Environment
Reproduction
Isolated reproduction:
https://stackblitz.com/edit/nuxt-starter-xti8mf?file=app.vue,package.json,app.spec.ts,components%2FFetching.spec.ts,components%2FFetching.vue,nuxt.config.ts
run
yarn vitest
to see a failed spec that imo shouldve succeedDescribe the bug
When using
registerEndpoint
to mock an api response I'd expect to be able to validate the correct dom is displayed based on the mock response.Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: