Added code coverage workflow to test the code coverage from unit and e2e tests#657
Added code coverage workflow to test the code coverage from unit and e2e tests#657msrathore-db merged 4 commits intomainfrom
Conversation
|
Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase ( |
|
Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase ( |
|
Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase ( |
jprakash-db
left a comment
jprakash-db
left a comment
There was a problem hiding this comment.
Overall LGTM. Since the coverage is above 85%. You can add the tests to fail if coverage drops below 85 %
|
Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase ( |
2 participants
What type of PR is this?
Description
Added code coverage workflow to test the code coverage from unit and e2e tests.
How is this tested?
Added some untested functions and unit tests to see if the check is sensitive to new additions.
Used act to locally test the workflow.
Related Tickets & Documents
PECOBLR-621