Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Can we collect code coverage? #70

Closed
bahmutov opened this issue May 7, 2020 · 2 comments · Fixed by #71
Closed

Can we collect code coverage? #70

bahmutov opened this issue May 7, 2020 · 2 comments · Fixed by #71
Labels
difficulty: hard 🧗‍♀️ impact: 🥇 released

Comments

@bahmutov
Copy link
Owner

bahmutov commented May 7, 2020

That would be very nice
@bahmutov bahmutov mentioned this issue May 7, 2020
Merged
@bahmutov
Copy link
Owner Author

bahmutov commented May 7, 2020

🎉 This issue has been resolved in version 2.2.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@alejandroiglesias
Copy link

I implemented the coverage as instructed but it seems to work for the template and not for the code in the <script> tags. It may be related to this issue. Is there any way to have coverage for the full component code that is not documented in the README of this project? I'm using @bahmutov/cy-rollup as instructed in the README. Thanks in advance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
difficulty: hard 🧗‍♀️ impact: 🥇 released
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: get code coverage from component tests bahmutov/cypress-svelte-unit-test
2 participants
@alejandroiglesias @bahmutov