fix: e2e tests are configured with project's nuxt.config #670
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
End to end tests should be as close to the real thing as possible, re-creating a whole separate Nuxt configuration from scratch adds potential for inconsistencies.
Context
Being new to Nuxt I was bashing my head against why Nuxt e2e tests didn't have
$axios
configured, and why my project would fail to evaluate the components I referenced in layout files.I also noticed that global css didn't work.
All of this because the
nuxt.config.js
wasn't being referenced in the end to end tests.