🌱 OPRUN-4849: Enable standalone ClusterObjectDeployment E2E scenarios

test/e2e/object-controller/features/cod_handoff.feature

@@ -1,4 +1,4 @@
-@BoxcutterRuntime
+@ObjectController @ClusterObjectDeployment
 Feature: ClusterObjectDeployment multi-revision handoff
 
   As an OLM user applying a ClusterObjectDeployment, I want a blocked successor
@@ -8,7 +8,7 @@ Feature: ClusterObjectDeployment multi-revision handoff
   that rollouts are safe and leave no orphaned content behind.
 
   Background:
-    Given OLM is available
+    Given object-controller is available
 
   # While the successor revision cannot take ownership of its objects it never
   # becomes Ready, so both revisions remain and the deployment reports the hard

test/e2e/object-controller/features/cod_lifecycle.feature

@@ -1,4 +1,4 @@
-@BoxcutterRuntime
+@ObjectController @ClusterObjectDeployment
 Feature: ClusterObjectDeployment group isolation and deletion
 
   As an OLM user running several ClusterObjectDeployments, I want each deployment
@@ -7,7 +7,7 @@ Feature: ClusterObjectDeployment group isolation and deletion
   another and leave nothing behind.
 
   Background:
-    Given OLM is available
+    Given object-controller is available
 
   # Two deployments allocate distinct groups and must not adopt each other's
   # revisions: each owns exactly its own revision (the owns step verifies the

test/e2e/object-controller/features/cod_progressing_reasons.feature

@@ -1,4 +1,4 @@
-@BoxcutterRuntime
+@ObjectController @ClusterObjectDeployment
 Feature: ClusterObjectDeployment impeded-rollout Progressing reasons
 
   As an OLM user applying a ClusterObjectDeployment, I want the Progressing
@@ -9,7 +9,7 @@ Feature: ClusterObjectDeployment impeded-rollout Progressing reasons
   directs me to inspect it for the specific cause.
 
   Background:
-    Given OLM is available
+    Given object-controller is available
 
   # A revision that cannot take ownership of its objects will not become Ready
   # without user action, so the deployment reports Progressing=False.

test/e2e/object-controller/features/cod_revision_history.feature

@@ -1,4 +1,4 @@
-@BoxcutterRuntime
+@ObjectController @ClusterObjectDeployment
 Feature: ClusterObjectDeployment revision history limit
 
   As an OLM user applying a ClusterObjectDeployment, I want archived (superseded)
@@ -7,7 +7,7 @@ Feature: ClusterObjectDeployment revision history limit
   available for inspection and rollback.
 
   Background:
-    Given OLM is available
+    Given object-controller is available
 
   Scenario: Archived revisions beyond the revisionHistoryLimit are garbage collected
     Given namespace "${TEST_NAMESPACE}" is available

test/e2e/object-controller/features/cod_rollout.feature

@@ -1,4 +1,4 @@
-@BoxcutterRuntime
+@ObjectController @ClusterObjectDeployment
 Feature: ClusterObjectDeployment revision rollout
 
   As an OLM user applying a ClusterObjectDeployment, I want the controller to roll
@@ -7,7 +7,7 @@ Feature: ClusterObjectDeployment revision rollout
   and report availability on the Available condition.
 
   Background:
-    Given OLM is available
+    Given object-controller is available
 
   Scenario: ClusterObjectDeployment rolls out its initial revision
     Given namespace "${TEST_NAMESPACE}" is available

test/e2e/object-controller/features/cod_template_metadata.feature

@@ -1,4 +1,4 @@
-@BoxcutterRuntime
+@ObjectController @ClusterObjectDeployment
 Feature: ClusterObjectDeployment template metadata propagation
 
   As an OLM user applying a ClusterObjectDeployment, I want the labels and
@@ -7,7 +7,7 @@ Feature: ClusterObjectDeployment template metadata propagation
   reported on the deployment rather than silently stalling the rollout.
 
   Background:
-    Given OLM is available
+    Given object-controller is available
 
   Scenario: Template metadata is propagated to the revision
     Given namespace "${TEST_NAMESPACE}" is available