@camunda/e2e-test-suite 0.0.920 → 0.0.922
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.
|
@@ -1146,10 +1146,16 @@ class ModelerCreatePage {
|
|
|
1146
1146
|
.getByText('Deploy process')
|
|
1147
1147
|
.locator('..')
|
|
1148
1148
|
.getByRole('button', { name: 'Deploy' });
|
|
1149
|
-
//
|
|
1150
|
-
//
|
|
1151
|
-
//
|
|
1152
|
-
|
|
1149
|
+
// The button reads "Configure test case" since camunda-hub a90fd06 and
|
|
1150
|
+
// "Configure scenario" before it. camunda-hub b3958a1649 then renamed its
|
|
1151
|
+
// test id from `play-configuration-configure-scenario-button` to
|
|
1152
|
+
// `configure-test-case-button` (see
|
|
1153
|
+
// TestMode/ConfigurationOverlay/index.tsx). Accept the pre-rename test id
|
|
1154
|
+
// too so the page object works either side of the rename.
|
|
1155
|
+
const configureScenarioButton = this.page
|
|
1156
|
+
.getByTestId('configure-test-case-button')
|
|
1157
|
+
.or(this.page.getByTestId('play-configuration-configure-scenario-button'))
|
|
1158
|
+
.first();
|
|
1153
1159
|
// Wait up to 15s for EITHER the new-flow setup panel OR the legacy Continue
|
|
1154
1160
|
// button to appear. Using .or() avoids separate sequential timeouts that would
|
|
1155
1161
|
// both expire before the page finishes loading on a slow cluster.
|
|
@@ -890,10 +890,14 @@ class ModelerCreatePage {
|
|
|
890
890
|
.getByText('Deploy process')
|
|
891
891
|
.locator('..')
|
|
892
892
|
.getByRole('button', { name: 'Deploy' });
|
|
893
|
-
//
|
|
894
|
-
//
|
|
895
|
-
// the test id
|
|
896
|
-
|
|
893
|
+
// camunda-hub a90fd06 renamed this step to "Configure test case" AND
|
|
894
|
+
// renamed its test id to `configure-test-case-button` (see
|
|
895
|
+
// TestMode/ConfigurationOverlay/index.tsx). Accept the pre-rename test id
|
|
896
|
+
// too so the page object works either side of the rename.
|
|
897
|
+
const configureScenarioButton = this.page
|
|
898
|
+
.getByTestId('configure-test-case-button')
|
|
899
|
+
.or(this.page.getByTestId('play-configuration-configure-scenario-button'))
|
|
900
|
+
.first();
|
|
897
901
|
// Wait up to 15s for EITHER the new-flow setup panel OR the legacy Continue
|
|
898
902
|
// button to appear. Using .or() avoids separate sequential timeouts that would
|
|
899
903
|
// both expire before the page finishes loading on a slow cluster.
|
|
@@ -65,12 +65,16 @@ class PlayPage {
|
|
|
65
65
|
this.configureTestPanelStartButton = this.configureTestPanel.getByRole('button', { name: /^Start( with .*)?$/, exact: false });
|
|
66
66
|
this.notifications = page.locator('.cds--toast-notification');
|
|
67
67
|
// Hub PR #25327 (2026-06-22) removed the standalone "Save scenario" modal
|
|
68
|
-
// and moved recording into the
|
|
69
|
-
//
|
|
70
|
-
// "
|
|
71
|
-
//
|
|
72
|
-
//
|
|
73
|
-
|
|
68
|
+
// and moved recording into the side panel's detail view. The detail view
|
|
69
|
+
// renders a TextInput plus a primary "Save test case" button and emits a
|
|
70
|
+
// "Test case saved" toast via @camunda/c4-notifications — see
|
|
71
|
+
// TestCasesPanel/TestCases/TestCaseDetail/{index.tsx,use-test-case-editor.ts}.
|
|
72
|
+
// camunda-hub a90fd06 renamed the input id from "scenario-name" to
|
|
73
|
+
// "test-case-name"; accept the pre-rename id too.
|
|
74
|
+
this.scenarioDetailNameInput = page
|
|
75
|
+
.locator('input#test-case-name')
|
|
76
|
+
.or(page.locator('input#scenario-name'))
|
|
77
|
+
.first();
|
|
74
78
|
this.scenarioDetailSaveButton = page.getByRole('button', {
|
|
75
79
|
name: /^Save (scenario|test case)$/i,
|
|
76
80
|
});
|