docs: add section about test runners upgrade to migration guide #1923
+45
−0
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.
Why
Context: vuejs/vue-test-utils#1975 (comment)
As discussed, there are a couple of issues that the community faced while upgrading to
vue@3
+@vue/test-utils@^2
but that are not directly related to them.In an effort to make migrations smoother, a new section was added to the migration guide that lists some common problems with underlying test runners. These can be common, due to the fact that users took the opportunity to upgrade their test stack dependencies as well since they were already doing the testing library migration.
What
It adds a few issues with
jest
, it starts with an issue reported in the legacy test-utils repo and another one that I've personally faced.Hopefully, the community can see this as a headstart and add more to the
jest
chapter and also include advice for other test runners.