-
Notifications
You must be signed in to change notification settings - Fork 85
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
🐛 Fix helm chart e2e tests: MatchYAML to Equal #692
🐛 Fix helm chart e2e tests: MatchYAML to Equal #692
Conversation
- Modify helm test cases to use `.To(Equal())` instead of `.To(MatchYAML())` - Add new test resource for manager-defined scenario with no feature gates - Update some test resources with version bumps and minor spec modifications
Hi @rgeraskin. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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-sigs/prow repository. |
✅ Deploy Preview for kubernetes-sigs-cluster-api-operator ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
/ok-to-test |
/lgtm |
LGTM label has been added. Git tree hash: 1899a0c3b5d3fff8743bc39489ed1cd27f835b2a
|
Thank you! /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: furkatgofurov7 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 |
Thanks for the fast review 🙂 |
What this PR does
In this PR, I’ve reverted MatchYAML to Equal, fixed all the broken tests. Also, I discovered and fixed a bug in the core provider specification condition.
Why we need it:
While working on PR #688, I’ve observed that a significant number of Helm chart e2e tests are false positives. This is because the generated YAML files in the test/e2e/resources directory do not accurately reflect the expected results from the test cases.
I believe this issue arises because
MatchYAML
is being used instead ofEqual
(#549).MatchYAML
only compares the first YAML document within a file, as demonstrated in a quick example.