@camunda/e2e-test-suite 0.0.1235 → 0.0.1237

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/dist/pages/c8Run-8.10/OperateHomePage.d.ts

@@ -6,6 +6,8 @@ declare class OperateHomePage {
     readonly informationDialog: Locator;
     readonly editVariableButton: Locator;
     readonly variableValueInput: Locator;
+    readonly variableValueEditor: Locator;
+    readonly variableValueContent: Locator;
     readonly saveVariableButton: Locator;
     readonly editVariableSpinner: Locator;
     constructor(page: Page);

package/dist/pages/c8Run-8.10/OperateHomePage.js

@@ -9,6 +9,8 @@ class OperateHomePage {
     informationDialog;
     editVariableButton;
     variableValueInput;
+    variableValueEditor;
+    variableValueContent;
     saveVariableButton;
     editVariableSpinner;
     constructor(page) {
@@ -28,6 +30,21 @@ class OperateHomePage {
         });
         this.editVariableButton = page.getByTestId('edit-variable-button');
         this.variableValueInput = page.getByTestId('edit-variable-value');
+        // "The row is in write mode." InlineJsonEditor renders a CodeMirror
+        // instance carrying this test id only on its editable branch; the
+        // read-only branch renders ReadOnlyEditor instead, with no CodeMirror
+        // at all. The product's own suite resolves the editor the same way --
+        // see camunda/camunda
+        // qa/c8-orchestration-cluster-e2e-test-suite/pages/OperateHomePage.ts.
+        this.variableValueEditor = page.getByTestId('code-mirror-editor');
+        // The editable node *inside* that container. CodeMirror puts its
+        // contenteditable on `.cm-content`, so that -- not the container -- is
+        // what takes focus and what holds the text. Asserting focus on the
+        // container reports `inactive` even when the caret is correctly placed,
+        // because clicking the container focuses its contenteditable child.
+        this.variableValueContent = this.variableValueEditor
+            .locator('.cm-content')
+            .first();
         // Carbon icon-only buttons expose their accessible name via aria-labelledby
         // (tooltip text "Save") which overrides aria-label for computed accessible name.
         // Use a CSS attribute selector to match the raw aria-label attribute directly.
@@ -56,8 +73,34 @@ class OperateHomePage {
         throw new Error(`Failed to click the processes tab after ${maxRetries} attempts.`);
     }
     async clickEditVariableButton(variableName) {
-        const editVariableButton = 'variable-' + variableName;
-        await this.page.getByTestId(editVariableButton).getByLabel('Edit').click();
+        const editVariableButton = this.page
+            .getByTestId('variable-' + variableName)
+            .getByLabel('Edit');
+        await (0, test_1.expect)(editVariableButton).toBeVisible({ timeout: 30000 });
+        // The caller reaches this straight out of activeIconAssertion, which
+        // reloads the page while it polls for the status icon, so the variables
+        // panel is usually still mounting when the click lands. A click during
+        // that render resolves without raising and without effect: the row stays
+        // read-only, InlineJsonEditor keeps rendering ReadOnlyEditor, and the
+        // editor the next step needs is never created. Retry until write mode is
+        // actually active rather than asserting on the editor afterwards and
+        // reporting the dropped click as a missing element.
+        //
+        // Only click while the row is still read-only. Entering write mode
+        // replaces the Edit control, so once the click has taken, clicking again
+        // just waits out its timeout against an element that is gone or still
+        // being replaced -- which is what the retry did on the slower macOS and
+        // Windows runners, where the editor needs longer to mount than one
+        // iteration allowed: it re-clicked, exhausted the budget, and raised the
+        // click timeout instead of the state the row was actually in. Probing
+        // first keeps the retry for a genuinely dropped click and turns the slow
+        // case into what it should be, a wait.
+        await (0, test_1.expect)(async () => {
+            if (await editVariableButton.isVisible()) {
+                await editVariableButton.click({ timeout: 10000 });
+            }
+            await (0, test_1.expect)(this.variableValueEditor).toBeVisible({ timeout: 15000 });
+        }).toPass({ timeout: 90000 });
     }
     async clickVariableValueInput() {
         await this.variableValueInput.click();
@@ -69,15 +112,18 @@ class OperateHomePage {
         // Operate migrated this editor from Monaco to CodeMirror
         // (@uiw/react-codemirror; see camunda/camunda#62782) -- the editable
         // region is now a div.cm-content, not .monaco-editor, and it no longer
-        // exposes a Monaco-style .cursor element. clickEditVariableButton still
-        // triggers autoFocus, so wait for the content element to actually have
-        // focus (:focus) before sending events, same intent as the old cursor
-        // check. Scoped to the variable row to avoid matching other editors.
-        const variableRow = this.page.getByTestId('variable-testVariable');
-        await variableRow
-            .locator('.cm-content:focus')
-            .first()
-            .waitFor({ state: 'visible', timeout: 30000 });
+        // exposes a Monaco-style .cursor element.
+        //
+        // clickEditVariableButton has already established that the editor exists
+        // -- it retries the Edit click until it does -- so this only has to put
+        // the caret in it. Do not wait on focus arriving by itself: autoFocus
+        // fires when the editor mounts, which is before this runs, so a wait for
+        // `:focus` can only ever observe focus that has already been placed
+        // elsewhere. Click to focus, then confirm. Both act on the
+        // contenteditable rather than its container, which cannot hold focus.
+        await (0, test_1.expect)(this.variableValueContent).toBeVisible({ timeout: 30000 });
+        await this.variableValueContent.click();
+        await (0, test_1.expect)(this.variableValueContent).toBeFocused({ timeout: 10000 });
         // Insert the COMPLETE JSON value, both quotes included. Monaco used to
         // auto-close a lone opening quote, so the old recipe inserted only
         // `"value`; CodeMirror's closeBrackets extension ignores insertions
@@ -97,7 +143,9 @@ class OperateHomePage {
         await this.page.keyboard.press('Backspace');
         const jsonValue = JSON.stringify(newValue);
         await this.page.keyboard.insertText(jsonValue);
-        await (0, test_1.expect)(variableRow.locator('.cm-content').first()).toContainText(jsonValue, { timeout: 10000 });
+        await (0, test_1.expect)(this.variableValueContent).toContainText(jsonValue, {
+            timeout: 10000,
+        });
     }
     async clickSaveVariableButton() {
         await this.saveVariableButton.click({ timeout: 30000 });

package/package.json

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