Open willie-yao opened 1 year ago
Hi @willie-yao I can take this one by one, but I need little more context, can youhelp?
Awesome @aniruddha2000, thanks for working on this! Basically, most controllers and reconcilers within the controllers
package do not have unit tests, or have very basic ones. I have created more detailed unit tests for the AzureMachine controller and reconciler as an example, and you can implement tests for other controllers similar to it: #3360
@willie-yao can you create the issue for next azurecluster_reconciler.go as well? I will start this week if possible
the AzureClusterReconciler is done as we discuss, can you create the issue for the next one @willie-yao ?
@aniruddha2000 Done, feel free to assign yourself when you're ready to work on it!
@willie-yao I was going to create an issue for the azuremanagedcluster_controller unit test and assign it to myself. I can update this issue when that is done.
The issue is linked above but here is the link to edit the intial description: https://github.com/kubernetes-sigs/cluster-api-provider-azure/issues/4270
New issue created https://github.com/kubernetes-sigs/cluster-api-provider-azure/issues/4277
PR is coming soon.
New issue created https://github.com/kubernetes-sigs/cluster-api-provider-azure/issues/4290
PR is coming soon
/reopen
This was closed because it was listed on the PR I submitted. (Won't do that again)
@troy0820: Reopened this issue.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
/lifecycle frozen
Keeping this at frozen to not close
/kind cleanup
What needs cleanup: This mega issue is meant to track individual issues for improving code coverage within the
controllers
package.Describe the solution you'd like
Older parent issue: https://github.com/kubernetes-sigs/cluster-api-provider-azure/issues/3229