-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added test for Fetcher fetchRoute + other stuff :) #103
Added test for Fetcher fetchRoute + other stuff :) #103
Conversation
p1pchenk0
commented
May 25, 2023
- test for fetcher
- failing unit tests after updates
* failing unit tests after updates
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## nuxt3 nuxt/nuxt-vitest#103 +/- ##
==========================================
+ Coverage 95.48% 95.82% +0.33%
==========================================
Files 54 55 +1
Lines 3898 3926 +28
Branches 590 604 +14
==========================================
+ Hits 3722 3762 +40
+ Misses 176 164 -12
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
Fab, thanks, good to merge or do you want to keep working on this branch tomorrow? |
yes, I think it would be the best option to continue working here |
* moved boolean check from ComponentGroup template to computed
…g and mocking * unskip tests for route middleware
}) | ||
}) | ||
|
||
test.todo('should return correct values for client/server flags IF env is server-side', () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, please add a comment Disabled due to nuxt-vitest bug - track issue and progress here https://github.com/danielroe/nuxt-vitest/issues/162