-
Notifications
You must be signed in to change notification settings - Fork 95
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
REFACTORING: Use DepResover mock in constroller tests #923
Labels
Milestone
Comments
kuritka
added a commit
that referenced
this issue
Sep 12, 2022
@kuritka what's the status of this one, can we close it? |
Hi, not fully. Depresolver mock for tests is ready (#951), but controller tests would be refactored, to use this mock instead of direct instanptiating. Coverage requirement is still met but it's more about unify controller tests with mocks. |
Closed
Stale issue, feel free to reopen if needed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Use DepResover mock instead of
settings := provideSettings(t, predefinedConfig)
in constroller tests.Using the settings object and calling reconcile is no longer sufficient. For example, the function works with
k8gb.absa.oss_v1beta1_gslb_cr.yaml
from which it generates a gslb for the tests. Any change to this file willcause the test to crash. We now have a depressolver mock (and a number of other mocks) that we can use for testing.
The text was updated successfully, but these errors were encountered: