-
Notifications
You must be signed in to change notification settings - Fork 928
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
operator/pkg/tasks/init: unit test karmada resource #5701
base: master
Are you sure you want to change the base?
operator/pkg/tasks/init: unit test karmada resource #5701
Conversation
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #5701 +/- ##
==========================================
- Coverage 39.09% 38.72% -0.38%
==========================================
Files 650 650
Lines 45209 55132 +9923
==========================================
+ Hits 17676 21350 +3674
- Misses 26180 32413 +6233
- Partials 1353 1369 +16
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
09c5c2f
to
f77d62c
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
f77d62c
to
3e6f5f3
Compare
In this commit, we unit test karmada resource init task on running karmada resources, system namespaces, crds, webhook configurations, and api service. Signed-off-by: Mohamed Awnallah <mohamedmohey2352@gmail.com>
3e6f5f3
to
6630227
Compare
cc @XiShanYongYe-Chang All unit test cases & linting issues passed after rebasing on the master branch :) |
Description
In this commit, we unit test karmada resource init task on running karmada resources, system namespaces, crds, webhook configurations, and api service.
What type of PR is this?
Which issue(s) this PR fixes:
Part of #5491.
Does this PR introduce a user-facing change?: