Skip to content

🌱 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.

Sign up for GitHub

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

Merged
openshift-merge-bot merged 2 commits into from
Jan 30, 2026
+61 −0
Merged

🌱 test: ensure single/own namespace increase coverage for both runtimes #2463

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
533c4e8
test: ensure single/own namespace increase coverage for both runtimes
camilamacedo86 Jan 28, 2026
feeed73
test: improve error message assertions for validation scenarios
camilamacedo86 Jan 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
61 changes: 61 additions & 0 deletions test/e2e/features/install.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -298,6 +298,67 @@ Feature: Install ClusterExtension
mutate: true
"""

@SingleOwnNamespaceInstallSupport
Scenario: Report failure when watchNamespace has invalid DNS-1123 name
Given ServiceAccount "olm-admin" in test namespace is cluster admin
When ClusterExtension is applied
"""
apiVersion: olm.operatorframework.io/v1
kind: ClusterExtension
metadata:
name: ${NAME}
spec:
namespace: ${TEST_NAMESPACE}
serviceAccount:
name: olm-admin
config:
configType: Inline
inline:
watchNamespace: invalid-namespace-
source:
sourceType: Catalog
catalog:
packageName: single-namespace-operator
selector:
matchLabels:
"olm.operatorframework.io/metadata.name": test-catalog
"""
Then ClusterExtension reports Progressing as True with Reason Retrying and Message includes:
"""
invalid ClusterExtension configuration: invalid configuration: field "watchNamespace" must match pattern
"""

@SingleOwnNamespaceInstallSupport
@WebhookProviderCertManager
Scenario: Reject watchNamespace for operator that does not support Single/OwnNamespace install modes
Given ServiceAccount "olm-admin" in test namespace is cluster admin
When ClusterExtension is applied
"""
apiVersion: olm.operatorframework.io/v1
kind: ClusterExtension
metadata:
name: ${NAME}
spec:
namespace: ${TEST_NAMESPACE}
serviceAccount:
name: olm-admin
config:
configType: Inline
inline:
watchNamespace: ${TEST_NAMESPACE}
source:
sourceType: Catalog
catalog:
packageName: webhook-operator
selector:
matchLabels:
"olm.operatorframework.io/metadata.name": test-catalog
"""
Then ClusterExtension reports Progressing as True with Reason Retrying and Message includes:
"""
invalid ClusterExtension configuration: invalid configuration: unknown field "watchNamespace"
"""

@BoxcutterRuntime
@ProgressDeadline
Scenario: Report ClusterExtension as not progressing if the rollout does not complete within given timeout
Expand Down