@camunda/e2e-test-suite 0.0.1109 → 0.0.1111

package/dist/pages/8.10/ModelerCreatePage.js

@@ -1567,9 +1567,8 @@ class ModelerCreatePage {
             // has nothing to deploy and renders no Deploy button at all.
             const alreadyDeployed = (await isDeployReported()) ||
                 (await configureScenarioButton
-                    .isVisible({ timeout: 3000 })
-                    .catch(() => false)) ||
-                (await configureTestPanel.isVisible().catch(() => false));
+                    .isEnabled({ timeout: 3000 })
+                    .catch(() => false));
             if (!alreadyDeployed) {
                 // Step 2: deploy — wait for enabled; button stays disabled until the cluster
                 // connection is confirmed by the backend after the Save in step 1.

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

@@ -1149,18 +1149,21 @@ class ModelerCreatePage {
             if (!alreadyDeployed) {
                 // Step 2: deploy
                 await setupDeployButton.click({ timeout });
-                // Test Studio dropped the "Process has been successfully deployed"
-                // toast: DeployStepContent now swaps the Deploy button for an inline
-                // `deploy-success-badge` ("Successfully deployed"), and
-                // TestConfigurationPanel's isDeployStepComplete effect calls
-                // hideConfigurationOverlay() as soon as deploy lands -- which
-                // collapses the Deploy step and opens "Configure test case" on its
-                // own. Accept either signal; a failed deploy renders a "Deployment
-                // failed" badge instead and matches neither.
-                await (0, test_1.expect)(this.page
-                    .getByTestId('deploy-success-badge')
-                    .or(configureTestPanel)
-                    .first()).toBeVisible({ timeout: 90000 });
+                // Deploy is done when the "Configure test case" button unlocks. There
+                // is no `deploy-success-badge` in the Test Studio DOM -- the overlay
+                // stays open with the deploy step showing a green check and that button
+                // enabled (this is how hub's own `Definition.setupEnvironment` e2e page
+                // object drives it: click Deploy, then click Configure, with no badge
+                // in between). On a build that auto-collapses the overlay the
+                // configure-test panel renders instead, so accept either. A failed
+                // deploy leaves the button disabled and the panel absent, so this still
+                // times out on a real deploy failure rather than masking it.
+                await (0, test_1.expect)(async () => {
+                    const deployComplete = (await configureScenarioButton
+                        .isEnabled({ timeout: 3000 })
+                        .catch(() => false)) || (await configureTestPanel.isVisible());
+                    (0, test_1.expect)(deployComplete).toBe(true);
+                }).toPass({ timeout: 90000 });
             }
             // Step 3: leave the overlay, and confirm we actually left it. The
             // button only calls hideConfigurationOverlay(); the overlay's own

package/dist/tests/8.10/play.spec.js

@@ -32,7 +32,15 @@ _8_10_1.test.describe('Deploy and run a process in Play', () => {
             });
         });
         await _8_10_1.test.step('Open Cross Component Test Project', async () => {
-            await modelerHomePage.clickCrossComponentProjectFolder();
+            // Self-healing variant: it clicks into the folder when the per-user
+            // setup project created it, and creates it first when that setup step
+            // did not take for this user. Clicking straight into the folder made a
+            // missing project an unrecoverable "Failed to click locator
+            // getByTitle('Cross Component Test Project')" five attempts later, even
+            // though the spec only needs *a* project to model in. Several sibling
+            // 8.10 specs (smoke-tests, rba-enabled-v2, access-user-role-management)
+            // already use this variant for the same reason.
+            await modelerHomePage.createCrossComponentProjectFolder();
         });
         await _8_10_1.test.step('Add A BPMN Template To The Project', async () => {
             await modelerHomePage.clickDiagramTypeDropdown();

package/package.json

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