@camunda/e2e-test-suite 0.0.923 → 0.0.924

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.
Files changed (6) hide show
  1. package/dist/pages/8.10/ModelerCreatePage.js +14 -6
  2. package/dist/pages/8.7/ModelerCreatePage.js +14 -4
  3. package/dist/pages/8.8/ModelerCreatePage.js +14 -4
  4. package/dist/pages/8.9/ModelerCreatePage.js +10 -6
  5. package/dist/pages/SM-8.10/ModelerCreatePage.js +10 -4
  6. package/package.json +1 -1
package/dist/pages/8.10/ModelerCreatePage.js CHANGED
@@ -1197,12 +1197,20 @@ class ModelerCreatePage {
1197
1197
  .getByText('Deploy process')
1198
1198
  .locator('..')
1199
1199
  .getByRole('button', { name: 'Deploy' });
1200
- // Keyed on the test id, not the label: the button reads "Configure test
1201
- // case" since camunda-hub a90fd06 and "Configure scenario" before it. The
1202
- // test id survived that rename but was itself renamed to match the label in
1203
- // camunda-hub b3958a1649 ("remove obsolete Play test mode feature flags"),
1204
- // so the old `play-configuration-*` id no longer exists in the DOM.
1205
- const configureScenarioButton = this.page.getByTestId('configure-test-case-button');
1200
+ // Both attributes on this button have been renamed by camunda-hub, in
1201
+ // separate commits: a90fd06 changed the label from "Configure scenario" to
1202
+ // "Configure test case", and b3958a1649 (#27259, 2026-08-07) then changed
1203
+ // the test id from `play-configuration-configure-scenario-button` to
1204
+ // `configure-test-case-button`. Match current test id, then pre-rename test
1205
+ // id, then either label, so a further rename of any single attribute cannot
1206
+ // break the step.
1207
+ const configureScenarioButton = this.page
1208
+ .getByTestId('configure-test-case-button')
1209
+ .or(this.page.getByTestId('play-configuration-configure-scenario-button'))
1210
+ .or(this.page.getByRole('button', {
1211
+ name: /^Configure (test case|scenario)$/,
1212
+ }))
1213
+ .first();
1206
1214
  // Wait up to 15s for EITHER the new-flow setup panel OR the legacy Continue
1207
1215
  // button to appear. Using .or() avoids separate sequential timeouts that would
1208
1216
  // both expire before the page finishes loading on a slow cluster.
package/dist/pages/8.7/ModelerCreatePage.js CHANGED
@@ -1049,10 +1049,20 @@ class ModelerCreatePage {
1049
1049
  .getByText('Deploy process')
1050
1050
  .locator('..')
1051
1051
  .getByRole('button', { name: 'Deploy' });
1052
- // Keyed on the test id, not the label: the button reads "Configure test
1053
- // case" since camunda-hub a90fd06 and "Configure scenario" before it, while
1054
- // the test id kept its original wording across the rename.
1055
- const configureScenarioButton = this.page.getByTestId('play-configuration-configure-scenario-button');
1052
+ // Both attributes on this button have been renamed by camunda-hub, in
1053
+ // separate commits: a90fd06 changed the label from "Configure scenario" to
1054
+ // "Configure test case", and b3958a1649 (#27259, 2026-08-07) then changed
1055
+ // the test id from `play-configuration-configure-scenario-button` to
1056
+ // `configure-test-case-button`. Match current test id, then pre-rename test
1057
+ // id, then either label, so a further rename of any single attribute cannot
1058
+ // break the step.
1059
+ const configureScenarioButton = this.page
1060
+ .getByTestId('configure-test-case-button')
1061
+ .or(this.page.getByTestId('play-configuration-configure-scenario-button'))
1062
+ .or(this.page.getByRole('button', {
1063
+ name: /^Configure (test case|scenario)$/,
1064
+ }))
1065
+ .first();
1056
1066
  // Wait up to 15s for EITHER the new-flow setup panel OR the legacy Continue
1057
1067
  // button to appear.
1058
1068
  const setupOrContinue = setupDeployButton.or(this.continueToPlayButton);
package/dist/pages/8.8/ModelerCreatePage.js CHANGED
@@ -1198,10 +1198,20 @@ class ModelerCreatePage {
1198
1198
  .getByText('Deploy process')
1199
1199
  .locator('..')
1200
1200
  .getByRole('button', { name: 'Deploy' });
1201
- // Keyed on the test id, not the label: the button reads "Configure test
1202
- // case" since camunda-hub a90fd06 and "Configure scenario" before it, while
1203
- // the test id kept its original wording across the rename.
1204
- const configureScenarioButton = this.page.getByTestId('play-configuration-configure-scenario-button');
1201
+ // Both attributes on this button have been renamed by camunda-hub, in
1202
+ // separate commits: a90fd06 changed the label from "Configure scenario" to
1203
+ // "Configure test case", and b3958a1649 (#27259, 2026-08-07) then changed
1204
+ // the test id from `play-configuration-configure-scenario-button` to
1205
+ // `configure-test-case-button`. Match current test id, then pre-rename test
1206
+ // id, then either label, so a further rename of any single attribute cannot
1207
+ // break the step.
1208
+ const configureScenarioButton = this.page
1209
+ .getByTestId('configure-test-case-button')
1210
+ .or(this.page.getByTestId('play-configuration-configure-scenario-button'))
1211
+ .or(this.page.getByRole('button', {
1212
+ name: /^Configure (test case|scenario)$/,
1213
+ }))
1214
+ .first();
1205
1215
  // Wait up to 15s for EITHER the new-flow setup panel OR the legacy Continue
1206
1216
  // button to appear. Using .or() avoids separate sequential timeouts that would
1207
1217
  // both expire before the page finishes loading on a slow cluster.
package/dist/pages/8.9/ModelerCreatePage.js CHANGED
@@ -1146,15 +1146,19 @@ class ModelerCreatePage {
1146
1146
  .getByText('Deploy process')
1147
1147
  .locator('..')
1148
1148
  .getByRole('button', { name: 'Deploy' });
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.
1149
+ // Both attributes on this button have been renamed by camunda-hub, in
1150
+ // separate commits: a90fd06 changed the label from "Configure scenario" to
1151
+ // "Configure test case", and b3958a1649 (#27259, 2026-08-07) then changed
1152
+ // the test id from `play-configuration-configure-scenario-button` to
1153
+ // `configure-test-case-button`. Match current test id, then pre-rename test
1154
+ // id, then either label, so a further rename of any single attribute cannot
1155
+ // break the step.
1155
1156
  const configureScenarioButton = this.page
1156
1157
  .getByTestId('configure-test-case-button')
1157
1158
  .or(this.page.getByTestId('play-configuration-configure-scenario-button'))
1159
+ .or(this.page.getByRole('button', {
1160
+ name: /^Configure (test case|scenario)$/,
1161
+ }))
1158
1162
  .first();
1159
1163
  // Wait up to 15s for EITHER the new-flow setup panel OR the legacy Continue
1160
1164
  // button to appear. Using .or() avoids separate sequential timeouts that would
package/dist/pages/SM-8.10/ModelerCreatePage.js CHANGED
@@ -890,13 +890,19 @@ class ModelerCreatePage {
890
890
  .getByText('Deploy process')
891
891
  .locator('..')
892
892
  .getByRole('button', { name: 'Deploy' });
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.
893
+ // Both attributes on this button have been renamed by camunda-hub, in
894
+ // separate commits: a90fd06 changed the label from "Configure scenario" to
895
+ // "Configure test case", and b3958a1649 (#27259, 2026-08-07) then changed
896
+ // the test id from `play-configuration-configure-scenario-button` to
897
+ // `configure-test-case-button`. Match current test id, then pre-rename test
898
+ // id, then either label, so a further rename of any single attribute cannot
899
+ // break the step.
897
900
  const configureScenarioButton = this.page
898
901
  .getByTestId('configure-test-case-button')
899
902
  .or(this.page.getByTestId('play-configuration-configure-scenario-button'))
903
+ .or(this.page.getByRole('button', {
904
+ name: /^Configure (test case|scenario)$/,
905
+ }))
900
906
  .first();
901
907
  // Wait up to 15s for EITHER the new-flow setup panel OR the legacy Continue
902
908
  // button to appear. Using .or() avoids separate sequential timeouts that would
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@camunda/e2e-test-suite",
3
- "version": "0.0.923",
3
+ "version": "0.0.924",
4
4
  "description": "End-to-end test helpers for Camunda 8",
5
5
  "repository": {
6
6
  "type": "git",