build: migrate tests to jest #1738
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kiaking
force-pushed
the
jest
branch
2 times, most recently
from
4131642
to
384b50f
Compare
Do you mean Cypress instead of Prettier? |
Sorry, I meant Puppeteer 🤦♂️ (fixed). I love Cypress! Though we're trying align with Vue 3. |
ktsn
reviewed
May 4, 2020
|
@ktsn Updated and also rebased to the latest branch 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Migrate test framework to Jest.
setupfiles out ofunitfilter and place it undertest. This is for migrating E2E test to use Puppeteer instead of Nightwatch. In that time, we should be able to reuse this file since the test will all run with Jest.babel-polyfilldue to deprecation. In the examples, we could add core-js pattern described here at the top.yarn coverageto generate test coverage.