This repository was archived by the owner on Dec 12, 2020. It is now read-only.
WIP: create wrapper component with vue test-utils #235
Conversation
This file contains hidden or 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
|
I'm having issues getting the tests to run. Locally it looked like everything ran successfully, but it bombed out while printing the results. Looks like travis couldn't start cypress. |
|
@NickBolles if you can resolve the merge conflicts, I have changed the CI, so it should be working now |
|
#365 is picking this up. I'm going to close this PR. 🙇♀️ |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I'm proposing creating a wrapper with vue-test-utils to use the utilities included with it. I'm not changing how the component is mounted, although it seems like we could do that to and remove some of the code included in this.
Is there a reason to avoid using vue-test-utils and cypress-vue-unit-test in tandem?