@camunda/e2e-test-suite 0.0.923 → 0.0.925

package/dist/pages/8.10/ModelerCreatePage.js

@@ -1197,12 +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. The
-        // test id survived that rename but was itself renamed to match the label in
-        // camunda-hub b3958a1649 ("remove obsolete Play test mode feature flags"),
-        // so the old `play-configuration-*` id no longer exists in the DOM.
-        const configureScenarioButton = this.page.getByTestId('configure-test-case-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/dist/utils/apiHelpers.js

@@ -6,6 +6,7 @@ Object.defineProperty(exports, "__esModule", { value: true });
 exports.updateClusterDataFilters = exports.getClusterDataFilters = exports.getTestClusterUuid = exports.authConsoleManagementAPI = exports.updateCollectionScope = exports.createSingleProcessReport = exports.createDashboard = exports.createCollection = exports.getOptimizeCookieSm = exports.getOptimizeCoockie = exports.createStringClusterVariable = exports.createJsonClusterVariable = exports.waitForProcessInstanceVisible = exports.createProcessInstance = exports.deployProcess = exports.waitForInboundWebhookRegistered = exports.waitForConnectorsReady = exports.validateMcpServerHealth = exports.authC8runAPI = exports.authSmAPI = exports.authSaasAPI = exports.authAPI = exports.buildZeebeApiUrl = exports.retryOn500 = exports.sendRequestAndAssertResponse = exports.assertUnauthorizedResponseBody = exports.expectUnauthorizedErrorBody = exports.assertResponseStatus = exports.getApiRequestContext = void 0;
 const test_1 = require("@playwright/test");
 const sleep_1 = require("./sleep");
+const randomSleep_1 = require("./randomSleep");
 const fs_1 = __importDefault(require("fs"));
 const path_1 = __importDefault(require("path"));
 const os_1 = __importDefault(require("os"));
@@ -604,7 +605,14 @@ async function createStringClusterVariable(authToken, environment = 'saas', cust
 exports.createStringClusterVariable = createStringClusterVariable;
 async function getOptimizeCoockie(page) {
     const optimizeUrl = process.env.CAMUNDA_OPTIMIZE_BASE_URL;
-    const maxLoginAttempts = 3;
+    const maxLoginAttempts = 4;
+    // This hook runs once per worker that picks up any test from an Optimize
+    // describe, so with 37 workers dozens of full interactive Auth0 logins for
+    // the same user fire within the same second. Stagger the first navigation to
+    // spread that burst -- it is enough on its own to trip Auth0's tenant-wide
+    // rate limit, which then fails every worker at once. Retries back off via
+    // randomSleep below, so this only needs to run once.
+    await (0, randomSleep_1.randomSleep)(0, 15000);
     // Auth0 can fail or rate-limit concurrent logins. Retry the whole flow if
     // loginToApp throws (e.g. waitForURL times out after a bad Auth0 redirect).
     for (let loginAttempt = 0; loginAttempt < maxLoginAttempts; loginAttempt++) {
@@ -616,9 +624,18 @@ async function getOptimizeCoockie(page) {
         }
         catch (error) {
             if (loginAttempt < maxLoginAttempts - 1) {
+                const rateLimited = String(error).includes(utils_1.AUTH0_RATE_LIMIT);
                 console.warn(`getOptimizeCoockie: login attempt ${loginAttempt + 1} failed, retrying after backoff...`, error);
                 await page.goto('about:blank');
-                await page.waitForTimeout(5000 * (loginAttempt + 1));
+                if (rateLimited) {
+                    // Auth0 rate-limit windows commonly last 30-90s. Back off long
+                    // enough to outlast the window; a 5-10s backoff just retries inside
+                    // the same window and burns the attempt budget for nothing.
+                    await (0, randomSleep_1.randomSleep)(60000, 90000);
+                }
+                else {
+                    await (0, randomSleep_1.randomSleep)(10000, 20000);
+                }
             }
             else {
                 throw error;

package/dist/utils/utils.d.ts

@@ -1,2 +1,3 @@
 import { Page } from '@playwright/test';
+export declare const AUTH0_RATE_LIMIT = "AUTH0_RATE_LIMIT";
 export declare function loginToApp(appName: string, page: Page): Promise<void>;

package/dist/utils/utils.js

@@ -1,25 +1,50 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.loginToApp = void 0;
+exports.loginToApp = exports.AUTH0_RATE_LIMIT = void 0;
 const test_1 = require("@playwright/test");
 const LoginPage_1 = require("../pages/8.8/LoginPage");
+exports.AUTH0_RATE_LIMIT = 'AUTH0_RATE_LIMIT';
+async function throwIfRateLimited(loginPage) {
+    const rateLimited = await loginPage.rateLimitError
+        .first()
+        .isVisible()
+        .catch(() => false);
+    if (rateLimited) {
+        throw new Error(`${exports.AUTH0_RATE_LIMIT}: identity provider returned an error page`);
+    }
+}
 async function loginToApp(appName, page) {
     await page.goto(appName, { waitUntil: 'domcontentloaded', timeout: 60000 });
     await page.waitForLoadState('networkidle', { timeout: 30000 }).catch(() => { });
     const loginPage = new LoginPage_1.LoginPage(page);
-    await (0, test_1.expect)(loginPage.usernameInput).toBeVisible({ timeout: 60000 });
+    // Auth0 serves a tenant-wide rate-limit error page that carries none of the
+    // usual auth controls. Settle on whichever of the two actually renders, then
+    // classify: waiting on usernameInput alone burns the full 60s before the
+    // caller can tell a rate limit apart from a slow login form, and the caller
+    // needs that distinction to pick a backoff long enough to outlast the window.
+    await (0, test_1.expect)(loginPage.usernameInput.or(loginPage.rateLimitError.first())).toBeVisible({ timeout: 60000 });
+    await throwIfRateLimited(loginPage);
     await loginPage.fillUsername(process.env.C8_USERNAME);
     await (0, test_1.expect)(loginPage.usernameInput).toHaveValue(process.env.C8_USERNAME);
     await (0, test_1.expect)(loginPage.loginMessage).toBeVisible();
     await loginPage.clickContinueButton();
-    await (0, test_1.expect)(loginPage.passwordInput).toBeVisible({ timeout: 90000 });
+    await (0, test_1.expect)(loginPage.passwordInput.or(loginPage.rateLimitError.first())).toBeVisible({ timeout: 90000 });
+    await throwIfRateLimited(loginPage);
     await loginPage.fillPassword(process.env.C8_PASSWORD);
     await (0, test_1.expect)(loginPage.passwordHeading).toBeVisible({ timeout: 90000 });
     await loginPage.clickLoginButton();
-    await page.waitForURL((url) => url.toString().startsWith(appName), {
-        timeout: 60000,
-        waitUntil: 'commit',
-    });
+    try {
+        await page.waitForURL((url) => url.toString().startsWith(appName), {
+            timeout: 60000,
+            waitUntil: 'commit',
+        });
+    }
+    catch (error) {
+        // Auth0 can also serve the rate-limit page as the response to the password
+        // submit, in which case the redirect back to appName never happens.
+        await throwIfRateLimited(loginPage);
+        throw error;
+    }
     await page
         .waitForLoadState('domcontentloaded', { timeout: 30000 })
         .catch(() => { });

package/package.json

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