@camunda/e2e-test-suite 0.0.922 → 0.0.924

package/dist/pages/8.10/ModelerCreatePage.d.ts

@@ -107,6 +107,7 @@ declare class ModelerCreatePage {
     constructor(page: Page);
     clickSecondDeployButton(): Promise<void>;
     modelJobWorkerDiagram(processName: string, embedFrom?: boolean, processId?: string): Promise<void>;
+    private waitForDiagramEditorToLoad;
     modelCamundaUserTaskDiagram(processName: string, processId?: string, formName?: string): Promise<void>;
     assignToCandidateGroup(taskName: string, candidateGroup: string, assignee?: string): Promise<void>;
     assignToCandidateUser(taskName: string, candidateUser: string, assignee?: string): Promise<void>;

package/dist/pages/8.10/ModelerCreatePage.js

@@ -357,10 +357,29 @@ class ModelerCreatePage {
         await this.clickAppendEndEventButton();
         await (0, sleep_1.sleep)(20000);
     }
+    // Opening the freshly created diagram occasionally lands on a bare gateway
+    // error page instead of the editor (the nightly captured Envoy's "upstream
+    // connect error or disconnect/reset before headers" plain-text response). That
+    // page never renders the properties panel, so one long wait just burns the
+    // whole budget before failing; reload between attempts so the blip recovers.
+    async waitForDiagramEditorToLoad() {
+        const maxAttempts = 3;
+        for (let attempt = 0; attempt < maxAttempts; attempt++) {
+            try {
+                await (0, test_1.expect)(this.generalPanel).toBeVisible({ timeout: 60000 });
+                return;
+            }
+            catch (error) {
+                if (attempt === maxAttempts - 1) {
+                    throw error;
+                }
+                console.warn(`Diagram editor did not load on attempt ${attempt + 1}; reloading.`);
+                await this.page.reload();
+            }
+        }
+    }
     async modelCamundaUserTaskDiagram(processName, processId = '', formName = '') {
-        await (0, test_1.expect)(this.generalPanel).toBeVisible({
-            timeout: 180000,
-        });
+        await this.waitForDiagramEditorToLoad();
         await this.enterDiagramName(processName);
         await (0, sleep_1.sleep)(15000);
         if (processId.length > 0) {
@@ -663,9 +682,36 @@ class ModelerCreatePage {
     async clickEditDiagramNameButton() {
         await this.renameDiagramNameButton.click({ timeout: 10000 });
     }
+    // The rename can silently no-op: camunda-hub's breadcrumb name editor
+    // (InlineEditable) resets its input back to the stored diagram name whenever
+    // the diagram store pushes a new value, and `renameDiagram` returns early when
+    // the submitted name equals the stored one — so an Enter that races the
+    // editor's initial autosave commits nothing. The diagram then keeps its
+    // "New BPMN diagram" default name, and every later lookup by process name
+    // (Operate's instance list, Tasklist, Play) can never match, which is what the
+    // nightly showed: three instances deployed as "New BPMN diagram". Confirm the
+    // name landed in the breadcrumb and re-open the editor to retry if it didn't.
     async enterDiagramName(name) {
-        await this.diagramNameInput.fill(name, { timeout: 90000 });
-        await this.diagramNameInput.press('Enter', { timeout: 90000 });
+        const maxAttempts = 3;
+        for (let attempt = 0; attempt < maxAttempts; attempt++) {
+            if (attempt > 0) {
+                await this.clickDiagramBreadcrumb();
+                await this.clickEditDiagramNameButton();
+            }
+            await this.diagramNameInput.fill(name, { timeout: 90000 });
+            await this.diagramNameInput.press('Enter', { timeout: 90000 });
+            try {
+                await this.diagramNameBreadcrumb(name).waitFor({
+                    state: 'visible',
+                    timeout: 30000,
+                });
+                return;
+            }
+            catch {
+                console.warn(`Diagram rename to "${name}" did not commit on attempt ${attempt + 1}.`);
+            }
+        }
+        throw new Error(`Diagram name was not set to "${name}".`);
     }
     async clickVariableInput() {
         await this.variableInput.click({ timeout: 60000 });
@@ -1151,10 +1197,20 @@ class ModelerCreatePage {
             .getByText('Deploy process')
             .locator('..')
             .getByRole('button', { name: 'Deploy' });
-        // Keyed on the test id, not the label: the button reads "Configure test
-        // case" since camunda-hub a90fd06 and "Configure scenario" before it, while
-        // the test id kept its original wording across the rename.
-        const configureScenarioButton = this.page.getByTestId('play-configuration-configure-scenario-button');
+        // Both attributes on this button have been renamed by camunda-hub, in
+        // separate commits: a90fd06 changed the label from "Configure scenario" to
+        // "Configure test case", and b3958a1649 (#27259, 2026-08-07) then changed
+        // the test id from `play-configuration-configure-scenario-button` to
+        // `configure-test-case-button`. Match current test id, then pre-rename test
+        // id, then either label, so a further rename of any single attribute cannot
+        // break the step.
+        const configureScenarioButton = this.page
+            .getByTestId('configure-test-case-button')
+            .or(this.page.getByTestId('play-configuration-configure-scenario-button'))
+            .or(this.page.getByRole('button', {
+            name: /^Configure (test case|scenario)$/,
+        }))
+            .first();
         // Wait up to 15s for EITHER the new-flow setup panel OR the legacy Continue
         // button to appear. Using .or() avoids separate sequential timeouts that would
         // both expire before the page finishes loading on a slow cluster.

package/dist/pages/8.7/ModelerCreatePage.js

@@ -1049,10 +1049,20 @@ class ModelerCreatePage {
             .getByText('Deploy process')
             .locator('..')
             .getByRole('button', { name: 'Deploy' });
-        // Keyed on the test id, not the label: the button reads "Configure test
-        // case" since camunda-hub a90fd06 and "Configure scenario" before it, while
-        // the test id kept its original wording across the rename.
-        const configureScenarioButton = this.page.getByTestId('play-configuration-configure-scenario-button');
+        // Both attributes on this button have been renamed by camunda-hub, in
+        // separate commits: a90fd06 changed the label from "Configure scenario" to
+        // "Configure test case", and b3958a1649 (#27259, 2026-08-07) then changed
+        // the test id from `play-configuration-configure-scenario-button` to
+        // `configure-test-case-button`. Match current test id, then pre-rename test
+        // id, then either label, so a further rename of any single attribute cannot
+        // break the step.
+        const configureScenarioButton = this.page
+            .getByTestId('configure-test-case-button')
+            .or(this.page.getByTestId('play-configuration-configure-scenario-button'))
+            .or(this.page.getByRole('button', {
+            name: /^Configure (test case|scenario)$/,
+        }))
+            .first();
         // Wait up to 15s for EITHER the new-flow setup panel OR the legacy Continue
         // button to appear.
         const setupOrContinue = setupDeployButton.or(this.continueToPlayButton);

package/dist/pages/8.8/ModelerCreatePage.js

@@ -1198,10 +1198,20 @@ class ModelerCreatePage {
             .getByText('Deploy process')
             .locator('..')
             .getByRole('button', { name: 'Deploy' });
-        // Keyed on the test id, not the label: the button reads "Configure test
-        // case" since camunda-hub a90fd06 and "Configure scenario" before it, while
-        // the test id kept its original wording across the rename.
-        const configureScenarioButton = this.page.getByTestId('play-configuration-configure-scenario-button');
+        // Both attributes on this button have been renamed by camunda-hub, in
+        // separate commits: a90fd06 changed the label from "Configure scenario" to
+        // "Configure test case", and b3958a1649 (#27259, 2026-08-07) then changed
+        // the test id from `play-configuration-configure-scenario-button` to
+        // `configure-test-case-button`. Match current test id, then pre-rename test
+        // id, then either label, so a further rename of any single attribute cannot
+        // break the step.
+        const configureScenarioButton = this.page
+            .getByTestId('configure-test-case-button')
+            .or(this.page.getByTestId('play-configuration-configure-scenario-button'))
+            .or(this.page.getByRole('button', {
+            name: /^Configure (test case|scenario)$/,
+        }))
+            .first();
         // Wait up to 15s for EITHER the new-flow setup panel OR the legacy Continue
         // button to appear. Using .or() avoids separate sequential timeouts that would
         // both expire before the page finishes loading on a slow cluster.

package/dist/pages/8.9/ModelerCreatePage.js

@@ -1146,15 +1146,19 @@ class ModelerCreatePage {
             .getByText('Deploy process')
             .locator('..')
             .getByRole('button', { name: 'Deploy' });
-        // The button reads "Configure test case" since camunda-hub a90fd06 and
-        // "Configure scenario" before it. camunda-hub b3958a1649 then renamed its
-        // test id from `play-configuration-configure-scenario-button` to
-        // `configure-test-case-button` (see
-        // TestMode/ConfigurationOverlay/index.tsx). Accept the pre-rename test id
-        // too so the page object works either side of the rename.
+        // Both attributes on this button have been renamed by camunda-hub, in
+        // separate commits: a90fd06 changed the label from "Configure scenario" to
+        // "Configure test case", and b3958a1649 (#27259, 2026-08-07) then changed
+        // the test id from `play-configuration-configure-scenario-button` to
+        // `configure-test-case-button`. Match current test id, then pre-rename test
+        // id, then either label, so a further rename of any single attribute cannot
+        // break the step.
         const configureScenarioButton = this.page
             .getByTestId('configure-test-case-button')
             .or(this.page.getByTestId('play-configuration-configure-scenario-button'))
+            .or(this.page.getByRole('button', {
+            name: /^Configure (test case|scenario)$/,
+        }))
             .first();
         // Wait up to 15s for EITHER the new-flow setup panel OR the legacy Continue
         // button to appear. Using .or() avoids separate sequential timeouts that would

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

@@ -890,13 +890,19 @@ class ModelerCreatePage {
             .getByText('Deploy process')
             .locator('..')
             .getByRole('button', { name: 'Deploy' });
-        // camunda-hub a90fd06 renamed this step to "Configure test case" AND
-        // renamed its test id to `configure-test-case-button` (see
-        // TestMode/ConfigurationOverlay/index.tsx). Accept the pre-rename test id
-        // too so the page object works either side of the rename.
+        // Both attributes on this button have been renamed by camunda-hub, in
+        // separate commits: a90fd06 changed the label from "Configure scenario" to
+        // "Configure test case", and b3958a1649 (#27259, 2026-08-07) then changed
+        // the test id from `play-configuration-configure-scenario-button` to
+        // `configure-test-case-button`. Match current test id, then pre-rename test
+        // id, then either label, so a further rename of any single attribute cannot
+        // break the step.
         const configureScenarioButton = this.page
             .getByTestId('configure-test-case-button')
             .or(this.page.getByTestId('play-configuration-configure-scenario-button'))
+            .or(this.page.getByRole('button', {
+            name: /^Configure (test case|scenario)$/,
+        }))
             .first();
         // Wait up to 15s for EITHER the new-flow setup panel OR the legacy Continue
         // button to appear. Using .or() avoids separate sequential timeouts that would

package/package.json

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