Generate code coverage reports for packages #4946
Merged
Conversation
This file contains 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
lina128
approved these changes
Apr 28, 2021
There was a problem hiding this comment.
LGTM! Thank you Matt. Just for my understanding, we need to run yarn coverage in local, right? Is it possible to automate test coverage in nightly?
Reviewable status:
complete! 1 of 1 approvals obtained
|
Thanks for the review, Na! Currently, we have to run |
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.
Add a
yarn coveragecommand to packages to generate coverage reports.To see the logs from the Cloud Build CI, please join either our discussion or announcement mailing list.
This change is