-
Notifications
You must be signed in to change notification settings - Fork 889
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
Add UT for pkg/controllers/status/work_status_controller.go #3568
Add UT for pkg/controllers/status/work_status_controller.go #3568
Conversation
f46d80a
to
7994394
Compare
Signed-off-by: rayywu <rayywu@tencent.com>
7994394
to
1412b2d
Compare
Codecov Report
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. @@ Coverage Diff @@
## master #3568 +/- ##
==========================================
+ Coverage 54.37% 55.86% +1.48%
==========================================
Files 216 216
Lines 20025 20121 +96
==========================================
+ Hits 10889 11240 +351
+ Misses 8553 8276 -277
- Partials 583 605 +22
Flags with carried forward coverage won't be shown. Click here to find out more. |
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.
Thanks
/lgtm
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.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: RainbowMango The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Promote UT coverage
Which issue(s) this PR fixes:
Part of #3327
Does this PR introduce a user-facing change?:
NONE