Adding Jest to Vue App and setting up test files - #98
Merged
Conversation
Contributor
Author
monicakochofar
force-pushed
the
mk-jest-vue
branch
from
September 29, 2023 18:14
98ac699 to
5ff2064
Compare
BallardRobinett
approved these changes
Sep 29, 2023
BallardRobinett
left a comment
Contributor
There was a problem hiding this comment.
looking good! For some reason the sensorSideBarRoutes test is failing for me though and I can't figure out why. Do we want to get these to trigger on push with github actions for a future card?
nice work!
Contributor
Author
Contributor
Contributor
Author
|
@BallardRobinett so turns out was missing a capitalization in the import statement! try giving it another shot now just pushed a fix. strange that i never got the error on my end |
Contributor
|
all tests passing for me now, nice work |
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
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.





This one became a doozy because of the new vue/test-utils library syntax, and ensuring our tests recognize the Vuetify Library/Vue-feather library, etc.
Here are the changes:
commands
Ensure you are in
app_vuefolder from rootto run all tests:
to run a single test:
to view code coverage visually, ensure you have run
npm testfor the most recent, then open the following file in your browser: