@camunda/e2e-test-suite 0.0.1090 → 0.0.1091

package/dist/pages/8.10/FormJsPage.js

@@ -148,7 +148,22 @@ class FormJsPage {
             .isVisible()
             .catch(() => false);
         if (!isLegacyDialog) {
-            await (0, test_1.expect)(this.dialog.getByText(clusterName, { exact: false }).first()).toBeVisible({ timeout: 30000 });
+            const offered = await this.dialog
+                .getByText(clusterName, { exact: false })
+                .first()
+                .waitFor({ state: 'visible', timeout: 30000 })
+                .then(() => true)
+                .catch(() => false);
+            if (!offered) {
+                // Forget the binding before failing. The dialog lists exactly the
+                // clusters this application's stages point at, so a missing cluster
+                // means the binding did not take -- and no amount of reopening the
+                // dialog will make it appear. Clearing the record lets the caller's
+                // next attempt rebind instead of re-checking an unchanged dialog.
+                this.processApplicationPage.forgetStageCluster();
+                throw new Error(`The deploy dialog does not offer "${clusterName}": its stage ` +
+                    'binding did not take. It will be rebound on the next attempt.');
+            }
             return;
         }
         const healthyRegex = new RegExp(`${clusterName}[\\s\\S]*?HealthydevManage`);
@@ -200,7 +215,25 @@ class FormJsPage {
         await (0, test_1.expect)(this.dialog).toBeVisible({
             timeout: 30000,
         });
-        await this.selectCluster(clusterName);
+        // selectCluster clears the stage binding when the dialog does not offer the
+        // cluster, so ensureStageCluster rebinds here and reports that it
+        // navigated. Any other failure leaves the binding in place, it returns
+        // false, and the original error stands. This path has no surrounding retry
+        // loop, hence the one explicit second attempt.
+        try {
+            await this.selectCluster(clusterName);
+        }
+        catch (error) {
+            const rebound = await this.processApplicationPage.ensureStageCluster(clusterName);
+            if (!rebound) {
+                throw error;
+            }
+            await this.clickDeployButton();
+            await (0, test_1.expect)(this.dialog).toBeVisible({
+                timeout: 30000,
+            });
+            await this.selectCluster(clusterName);
+        }
         await this.selectOnlyThisResource();
         await this.clickDeploySubButton();
         await (0, test_1.expect)(this.deploySuccessNotification).toBeVisible({ timeout: 30000 });

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

@@ -22,6 +22,7 @@ declare class ProcessApplicationPage {
     nameNewProcessApplication(name: string): Promise<void>;
     defineDevelopmentStage(clusterName?: string): Promise<void>;
     rememberResourceContainer(url: string): void;
+    forgetStageCluster(): void;
     ensureStageCluster(clusterName: string): Promise<boolean>;
     private openStageDefinition;
     openByName(name: string): Promise<void>;

package/dist/pages/8.10/ProcessApplicationPage.js

@@ -196,6 +196,18 @@ class ProcessApplicationPage {
     rememberResourceContainer(url) {
         resourceContainers.set(this.page, { url });
     }
+    // Drops the recorded development-stage binding so the next ensureStageCluster
+    // call binds again. Called when the deploy dialog turns out not to offer the
+    // cluster we believe we bound: the dialog offers exactly what the
+    // application's stages point at, so if the cluster is missing the binding
+    // did not take, and reopening the dialog can never change that. Without
+    // this, a caller's retries all re-check a state nothing is changing.
+    forgetStageCluster() {
+        const container = resourceContainers.get(this.page);
+        if (container) {
+            container.developmentCluster = undefined;
+        }
+    }
     // A process application deploys to the clusters bound to its stages, and
     // nothing else: inside a container DeployModal renders
     // ProcessAppClusterSelection, which lists only those and auto-selects the

package/package.json

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