-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[KCP] Increase unit test coverage #2779
Comments
/area control-plane |
@sedefsavas: You must be a member of the kubernetes-sigs/cluster-api-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Cluster API Maintainers and have them propose you as an additional delegate for this responsibility. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/milestone v0.3.x |
Since this seems like a bit of work, I suggest we split the work by folder so multiple people can work on it for example, I can start working on some of the internal files without tests while someone else can pick other packages if they want to |
Good idea @nader-ziada |
/assign |
i'll take these
|
Are there any more areas that require testing in KCP? Should we close this issue? |
We can probably close this for now, we're tacking the rest in #2753 /close |
/milestone v0.3.4 |
@vincepri: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Following issue #2753, this issue is to track unit-test-coverage increase efforts.
There are several TODO unit tests are added to the test files.
We should focus on improving the current coverage which is as follows:
kubeadm/controllers:
kubeadm/internal:
The text was updated successfully, but these errors were encountered: