@camunda/e2e-test-suite 0.0.1275 → 0.0.1276

package/dist/pages/8.10/ClusterPage.js

@@ -280,7 +280,14 @@ class ClusterPage {
         await this.clickClusterNameInput();
         await this.fillClusterNameInput(name);
         await this.clickClusterType();
-        await this.page.getByRole('tab', { name: region }).click();
+        // Same design-system role="radio" fallback as the choice()-wrapped
+        // locators above -- `region` is a runtime parameter ('GCP'/'AWS') so
+        // this can't reuse a named locator directly. Ported from
+        // pages/8.9/ClusterPage.ts.
+        await this.page
+            .getByRole('tab', { name: region })
+            .or(this.page.getByRole('radio', { name: region, exact: true }))
+            .click();
         await this.selectSubRegion(region);
         await this.clickClusterOption();
         await this.determineTasklistAPI(tasklistV1Api);

package/dist/pages/8.10/ConsoleOrganizationPage.js

@@ -118,9 +118,16 @@ class ConsoleOrganizationPage {
             name: 'danger',
         })
             .last();
-        this.filterTableSearchbox = page.getByRole('searchbox', {
-            name: 'Filter table',
-        });
+        // Camunda Hub's design-system Organization Management page renamed the
+        // Carbon TableToolbarSearch's default "Filter table" label to plain
+        // "Search" (same rename already ported elsewhere for the secrets
+        // panels). Confirmed against camunda-hub's own
+        // e2e-playwright/pages/Console/ConsoleOrgManagementPage.ts, which already
+        // uses `getByRole('searchbox', {name: 'Search'})` for this exact users
+        // list. Match either.
+        this.filterTableSearchbox = page
+            .getByRole('searchbox', { name: 'Filter table' })
+            .or(page.getByRole('searchbox', { name: 'Search' }));
     }
     async filterTable(names) {
         for (const name of names) {

package/dist/pages/8.10/ProcessApplicationPage.js

@@ -48,21 +48,49 @@ class ProcessApplicationPage {
         // .first() defensively only: hub renders exactly one of these today, in the
         // workspace-root empty state. A future second placement should not turn
         // every PA-creating test into a strict-mode violation.
+        //
+        // hubTerm('project') (utils/hub-terminology.ts) renames "process
+        // application" to "project" in copy once an org has workspacesEnabled --
+        // confirmed from a nightly trace screenshot on hub.ultrawombat.com: the
+        // workspace-root empty state renders "Create project" (not "Create
+        // process application"), and EmptyStateActionButtons.tsx's source
+        // confirms the button text is `Create {hubTerm('project')}`. Accept both
+        // so this keeps working on orgs at either rollout stage.
+        // exact:true on both -- without it, "Create project" substring-matches
+        // the split button's own "Create project options" chevron too, and
+        // .first() then picks whichever the DOM happens to order first. Same
+        // pattern already fixed for the same chevron in
+        // ModelerHomePage.ts's createNewProjectButton/createWorkspaceButton.
         this.createProcessApplicationButton = page
-            .getByRole('button', { name: 'Create process application' })
+            .getByRole('button', { name: 'Create process application', exact: true })
+            .or(page.getByRole('button', { name: 'Create project', exact: true }))
             .first();
         this.createProcessApplicationOption = page.locator('[data-test="create-process-application"]');
-        this.creationDialog = page.getByRole('dialog', {
-            name: 'Create a process application',
-        });
+        // Same hubTerm('project') rename as the button above --
+        // CreationModalDs.common.tsx's dialog title is `Create a
+        // {hubTerm('project')}`. A confirmed nightly trace showed a THIRD shape,
+        // live on this SaaS org: `app/pages/workspace-projects/features/
+        // create-project/CreateProjectModal.tsx` -- a newer, unrelated component
+        // (built on `api/projects`' useCreateProject, not processApplicationStore)
+        // titled plainly "Create project" (no "a"), with its field labelled
+        // "Project name" (not "Name") and its submit button reading "Create
+        // project" (not "Create"). Accept all three shapes.
+        this.creationDialog = page
+            .getByRole('dialog', { name: 'Create a process application' })
+            .or(page.getByRole('dialog', { name: 'Create a project' }))
+            .or(page.getByRole('dialog', { name: 'Create project', exact: true }));
         // Deliberately scoped to the dialog: ModelerCreatePage owns an unscoped
         // getByLabel('Name', {exact: true}) for the properties panel, which would
         // resolve to two elements while the creation modal is open.
-        this.nameInput = this.creationDialog.getByLabel('Name', { exact: true });
-        this.submitButton = this.creationDialog.getByRole('button', {
-            name: 'Create',
+        this.nameInput = this.creationDialog
+            .getByLabel('Name', { exact: true })
+            .or(this.creationDialog.getByLabel('Project name', { exact: true }));
+        this.submitButton = this.creationDialog
+            .getByRole('button', { name: 'Create', exact: true })
+            .or(this.creationDialog.getByRole('button', {
+            name: 'Create project',
             exact: true,
-        });
+        }));
         this.cancelButton = this.creationDialog.getByRole('button', {
             name: 'Cancel',
             exact: true,

package/dist/pages/8.10/SettingsPage.js

@@ -7,8 +7,18 @@ class SettingsPage {
     logoutButton;
     constructor(page) {
         this.page = page;
-        this.openSettingsButton = page.getByLabel('Open Settings');
-        this.logoutButton = page.getByRole('button', { name: 'Log out' });
+        // Camunda Hub's design-system shell renders a `UserMenu` button named
+        // "User menu, <full name>" in place of the legacy Carbon "Open Settings"
+        // icon button, and its logout control is a menuitem inside that menu
+        // rather than a plain button. Both shells still ship -- match either.
+        // Ported from camunda-hub's own e2e-playwright/pages/Console/ConsoleBasePage.ts
+        // (settingsButton / dsLogoutMenuItem / carbonLogoutButton).
+        this.openSettingsButton = page
+            .getByRole('button', { name: /^User menu,/ })
+            .or(page.getByLabel('Open Settings'));
+        this.logoutButton = page
+            .getByRole('menuitem', { name: 'Log out', exact: true })
+            .or(page.getByRole('button', { name: 'Log out' }));
     }
     async clickOpenSettingsButton(retries = 3) {
         for (let i = 0; i < retries; i++) {

package/package.json

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