@camunda/e2e-test-suite 0.0.1236 → 0.0.1238

package/dist/pages/8.10/ModelerCreatePage.js

@@ -1653,7 +1653,7 @@ class ModelerCreatePage {
         const configurationOverlay = this.page
             .locator('[data-test="test-studio-configuration-overlay"]')
             .or(this.page.locator('[data-test="play-configuration-overlay"]'))
-            .or(this.page.getByText('Setup environment'))
+            .or(this.page.getByText('Set up environment'))
             .first();
         const configureTestPanel = this.page.getByTestId('configure-test-panel');
         await (0, test_1.expect)(configurationOverlay

package/dist/pages/SM-8.10/ModelerCreatePage.js

@@ -1076,7 +1076,7 @@ class ModelerCreatePage {
     }
     async completePlayConfiguration() {
         const timeout = 30000;
-        // New flow (8.10+): "Setup environment" panel with three steps:
+        // New flow (8.10+): "Set up environment" panel with three steps:
         //   1. Connect cluster → "Configure environment" modal → select cluster → Save
         //   2. Deploy process → wait for success banner
         //   3. Configure test case
@@ -1123,15 +1123,20 @@ class ModelerCreatePage {
         // clickStartInstanceButton burned its entire retry budget looking for it.
         // camunda-hub's "Play" -> "Test Studio" rebrand renamed this container's
         // data-test from `play-configuration-overlay` to
-        // `test-studio-configuration-overlay` (confirmed in the failing run's trace
-        // DOM), so the old gate matched nothing and timed out. Anchor on the new
-        // data-test, keep the legacy attribute for older modeler builds, and fall
-        // back to the "Setup environment" panel title. This locator means "the
-        // setup panel is still on screen".
+        // `test-studio-configuration-overlay`, and a later build dropped both
+        // container data-test attributes entirely (neither is present in the
+        // failing run's trace DOM), so those two gates now match nothing. The
+        // always-present anchor is the panel's heading, which the current build
+        // renders as "Set up environment" (verb, two words) -- the old
+        // `getByText('Setup environment')` (one word) never matched it and the
+        // whole chain timed out. Match the heading with a spelling-tolerant regex
+        // so a future flip between the two forms cannot re-break the gate, and keep
+        // the legacy data-test attributes for older modeler builds. This locator
+        // means "the setup panel is still on screen".
         const configurationOverlay = this.page
             .locator('[data-test="test-studio-configuration-overlay"]')
             .or(this.page.locator('[data-test="play-configuration-overlay"]'))
-            .or(this.page.getByText('Setup environment'))
+            .or(this.page.getByText(/set ?up environment/i))
             .first();
         const configureTestPanel = this.page.getByTestId('configure-test-panel');
         await (0, test_1.expect)(configurationOverlay
@@ -1199,7 +1204,7 @@ class ModelerCreatePage {
                 }).toPass({ timeout: 90000 });
             }
             // Step 3: reveal the "Configure test case" section. In the current Test
-            // Studio the "Setup environment" panel is an inline accordion, not a
+            // Studio the "Set up environment" panel is an inline accordion, not a
             // blocking overlay -- its heading is always present and step 3 auto-opens
             // once deploy completes, rendering ConfigureTestPanel with the Start
             // button. Clicking the "Configure test case" accordion heading while it

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camunda/e2e-test-suite",
-  "version": "0.0.1236",
+  "version": "0.0.1238",
   "description": "End-to-end test helpers for Camunda 8",
   "repository": {
     "type": "git",