-
Notifications
You must be signed in to change notification settings - Fork 3
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
Setup Unit Test Coverage Reports for Deno Packages #63
Comments
@tnrich I think you've setup CodeCov for OVE... can you help us get unit tests and coverage setup for the FSML code? |
@tnrich were you able to get this working? |
@tgadam nope, not able to get this working The deno coverage command doesn't seem to be working quite yet.. Seems like deno is still a bit immature at this point. |
@tgadam oh, looks like someone got back to me on the example! I'll work through the example and see if that gets me unblocked. |
@tgadam I was able to get the coverage generating properly for the oak repo but for some reason running the same commands locally does not seem to work.. not sure what is going wrong.. |
@tnrich I noticed the oak example uses import maps. I was planning on moving us to using import maps but hadn't done it yet. Maybe that's part of what we need to do? |
@tgadam potentially? Not sure why that would be necessary but I suppose it might be |
@tgadam I tried fiddling with the import-map and was unable to get coverage working with that either.. Not sure what the issue is here. |
Lol looking more closely reveals that we're not actually importing any src files into our test. That might be at the source of this 😆 |
It seems that this was covered in #87. I'm moving this to "merged". |
Setup Unit Test Coverage Reports for Deno Packages and hook it up to CodeCov for OpenSource using GitHub Actions.
The text was updated successfully, but these errors were encountered: