-
Notifications
You must be signed in to change notification settings - Fork 71
🌱 test: ensure single/own namespace increase coverage for both runtimes #2463
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
🌱 test: ensure single/own namespace increase coverage for both runtimes #2463
Conversation
✅ Deploy Preview for olmv1 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
Pull request overview
Adds new E2E coverage for Single/OwnNamespace install behavior in ClusterExtension installation scenarios.
Changes:
- Adds a scenario asserting the extension retries when
watchNamespacepoints to a namespace that doesn’t exist. - Adds a scenario asserting a bundle that doesn’t support Single/OwnNamespace mode rejects
watchNamespaceconfig.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
990f1ea to
e44026d
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.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
e44026d to
b3a27c1
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2463 +/- ##
==========================================
- Coverage 69.48% 69.46% -0.03%
==========================================
Files 102 102
Lines 8249 8249
==========================================
- Hits 5732 5730 -2
- Misses 2063 2064 +1
- Partials 454 455 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
/approve |
test/e2e/features/install.feature
Outdated
| """ | ||
| Then ClusterExtension reports Progressing as True with Reason Retrying and Message includes: | ||
| """ | ||
| watchNamespace |
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.
I am adding the test cases.
When we fix the Boxcutter, we have the Reason Failed
We can supplement those tests to ensure that False and Reason Failed for those cases.
b3a27c1 to
a2274ef
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.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
a2274ef to
8ad72e8
Compare
Add E2E test scenarios for single/own namespace support that run for both Helm and Boxcutter runtimes: 1. Invalid DNS-1123 watchNamespace - tests namespace name validation 2. Reject watchNamespace for AllNamespaces-only operators Tests use assertions compatible with both runtimes. Unit tests in provider_test.go provide comprehensive validation coverage via shared RegistryV1ManifestProvider. Achieves 100% parity with downstream OCP test coverage.
8ad72e8 to
4b2a0cd
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.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Enhance both new test scenarios with more complete error message assertions: 1. DNS-1123 validation test: Now checks for the full error context including "invalid ClusterExtension configuration: invalid target namespaces [invalid-namespace-]: a lowercase RFC 1123 subdomain..." instead of just "lowercase RFC 1123". 2. AllNamespaces operator rejection test: Now verifies the complete error about "invalid ClusterExtension configuration: supported install modes [AllNamespaces] do not support target namespaces" instead of just "watchNamespace". These more comprehensive assertions better demonstrate that proper validation is occurring and provide clearer test documentation of the expected error behavior. Assisted-by: Claude Sonnet 4.5 <noreply@anthropic.com>
4b2a0cd to
feeed73
Compare
|
@pedjak All addressed could it win your LGTM now ? |
pedjak
left a comment
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: pedjak, tmshort The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
5c4bf7b
into
operator-framework:main
Add E2E test scenarios for single/own namespace support that run for
both Helm and Boxcutter runtimes:
Tests use assertions compatible with both runtimes. Unit tests in
provider_test.go provide comprehensive validation coverage via shared
RegistryV1ManifestProvider.
Achieves 100% parity with downstream OCP test coverage.