@camunda/e2e-test-suite 0.0.921 → 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
- // Keyed on the test id, not the label: the button reads "Configure test
1150
- // case" since camunda-hub a90fd06 and "Configure scenario" before it, while
1151
- // the test id kept its original wording across the rename.
1152
- const configureScenarioButton = this.page.getByTestId('play-configuration-configure-scenario-button');
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.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@camunda/e2e-test-suite",
3
- "version": "0.0.921",
3
+ "version": "0.0.922",
4
4
  "description": "End-to-end test helpers for Camunda 8",
5
5
  "repository": {
6
6
  "type": "git",