-
Notifications
You must be signed in to change notification settings - Fork 18
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
[envtest]Improve coverage #63
[envtest]Improve coverage #63
Conversation
8aef5ae
to
4d1437a
Compare
This adds a test case to show that placement-operator does not ensure that the expected fields are in the provided secret so it can generate wrong dbsync job configuration.
This increased or coverage from 38 to 70 percent
This is needed as we want to switch from the hardcoded "placement" PlacementAPI name to a generated one
This has two benefits: * shows where placement-operator hardcodes names instead of using the name of the PlacementAPI CR like in case of the db sync Job and the Deployment. * allows more test case independency
Now that the test global variable handling is improved the test can run in any order.
4d1437a
to
1f33842
Compare
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.
lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gibizer, mrKisaoLamb 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 |
98b1b73
into
openstack-k8s-operators:main
We now at least covering the happy deployment path.
Related: https://issues.redhat.com/browse/OSPRH-108