@camunda/e2e-test-suite 0.0.1109 → 0.0.1110
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -1149,18 +1149,21 @@ class ModelerCreatePage {
|
|
|
1149
1149
|
if (!alreadyDeployed) {
|
|
1150
1150
|
// Step 2: deploy
|
|
1151
1151
|
await setupDeployButton.click({ timeout });
|
|
1152
|
-
//
|
|
1153
|
-
//
|
|
1154
|
-
//
|
|
1155
|
-
//
|
|
1156
|
-
//
|
|
1157
|
-
//
|
|
1158
|
-
//
|
|
1159
|
-
//
|
|
1160
|
-
|
|
1161
|
-
|
|
1162
|
-
|
|
1163
|
-
|
|
1152
|
+
// Deploy is done when the "Configure test case" button unlocks. There
|
|
1153
|
+
// is no `deploy-success-badge` in the Test Studio DOM -- the overlay
|
|
1154
|
+
// stays open with the deploy step showing a green check and that button
|
|
1155
|
+
// enabled (this is how hub's own `Definition.setupEnvironment` e2e page
|
|
1156
|
+
// object drives it: click Deploy, then click Configure, with no badge
|
|
1157
|
+
// in between). On a build that auto-collapses the overlay the
|
|
1158
|
+
// configure-test panel renders instead, so accept either. A failed
|
|
1159
|
+
// deploy leaves the button disabled and the panel absent, so this still
|
|
1160
|
+
// times out on a real deploy failure rather than masking it.
|
|
1161
|
+
await (0, test_1.expect)(async () => {
|
|
1162
|
+
const deployComplete = (await configureScenarioButton
|
|
1163
|
+
.isEnabled({ timeout: 3000 })
|
|
1164
|
+
.catch(() => false)) || (await configureTestPanel.isVisible());
|
|
1165
|
+
(0, test_1.expect)(deployComplete).toBe(true);
|
|
1166
|
+
}).toPass({ timeout: 90000 });
|
|
1164
1167
|
}
|
|
1165
1168
|
// Step 3: leave the overlay, and confirm we actually left it. The
|
|
1166
1169
|
// button only calls hideConfigurationOverlay(); the overlay's own
|