@camunda/e2e-test-suite 0.0.897 → 0.0.899

package/dist/pages/8.8/ModelerCreatePage.js

@@ -127,7 +127,11 @@ class ModelerCreatePage {
         // ambiguous whenever a diagram name contains it (e.g. "Optimize Job Worker
         // User Task Diagram"). Target the built-in entry by its stable data-id.
         this.userTaskOption = page.locator('.djs-popup-results [data-id="replace-with-user-task"]');
-        this.priorityInput = page.getByRole('textbox', { name: 'priority' });
+        // The user-task priority field renders as `<input type="number">`, whose
+        // ARIA role is `spinbutton`, not `textbox`. Its id is also what separates it
+        // from the "Job priority" group's `jobPriorityDefinitionPriority` field,
+        // which any name-based query matches as well.
+        this.priorityInput = page.locator('#bio-properties-panel-priorityDefinitionPriority');
         this.appendEndEventButton = page.getByRole('button', {
             name: 'Append end event',
         });
@@ -504,11 +508,17 @@ class ModelerCreatePage {
         await this.page.waitForTimeout(1000);
     }
     async clickPriorityInput() {
+        // `.bio-properties-panel-group-header empty open` is a descendant
+        // combinator over non-existent `empty`/`open` element types, so it always
+        // counted 0 and every call clicked the group container blindly — toggling
+        // the section shut again on the second and later user tasks.
         const isExpanded = (await this.assignmentSection
-            .locator('.bio-properties-panel-group-header empty open')
+            .locator('.bio-properties-panel-group-header.open')
             .count()) > 0;
         if (!isExpanded) {
-            await this.assignmentSection.click();
+            await this.assignmentSection
+                .locator('.bio-properties-panel-group-header')
+                .click();
         }
         await this.priorityInput.click({ timeout: 30000 });
     }

package/dist/pages/SM-8.8/OCIdentityRolesPage.js

@@ -106,8 +106,19 @@ class OCIdentityRolesPage {
         await this.selectResourceTypeTab('Mapping Rules').click();
     }
     async clickRole(roleID) {
-        await (0, test_1.expect)(this.roleCell(roleID).first()).toBeVisible({ timeout: 60000 });
-        await this.roleCell(roleID).first().click();
+        // The Roles table can settle on a stale render after the Roles tab loads:
+        // a role returned by /orchestration/v2/roles/search is missing from the
+        // rendered rows (another role is duplicated in its place). Reload between
+        // attempts so the table refetches instead of waiting out the timeout on a
+        // render that will never update.
+        await (0, clickLocatorWithRetry_1.clickLocatorWithRetry)(this.page, this.roleCell(roleID).first(), {
+            visibilityTimeout: 30000,
+            totalTimeout: 120000,
+            maxRetries: 4,
+            postAction: async () => {
+                await this.page.reload({ waitUntil: 'domcontentloaded' });
+            },
+        });
     }
     async assignMappingRuleToRole(roleId, mappingId) {
         await this.clickRole(roleId);

package/dist/pages/SM-8.8/SettingsPage.js

@@ -1,6 +1,7 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.SettingsPage = void 0;
+const LoginPage_1 = require("./LoginPage");
 class SettingsPage {
     page;
     openSettingsButton;
@@ -19,7 +20,27 @@ class SettingsPage {
         await this.openUserSidebarButton.click({ timeout: 120000 });
     }
     async clickLogoutButton() {
+        const loginPage = new LoginPage_1.LoginPage(this.page);
+        // Logging out is *usually* a redirect chain (app -> OIDC end-session ->
+        // login page) -- wait for the login screen before returning so a caller
+        // resetting the session doesn't reload while that navigation is still in
+        // flight (aborts the reload with net::ERR_ABORTED). But a known identity
+        // bug (https://github.com/camunda/camunda/issues/32382) means the chain
+        // doesn't always complete: this can settle back on the still-authenticated
+        // app instead of a login screen (confirmed via CI screenshots -- the page
+        // stays on Identity > Mapping rules, fully logged in, both on first
+        // attempt and retry). Every caller of this method follows it with
+        // resetSession(), which force-clears cookies and reloads regardless of
+        // where this lands -- that's the actual, reliable logout here, so this
+        // wait is best-effort: give the redirect a chance to settle, but don't
+        // fail the test over a known bug that resetSession() already works around.
         await this.logoutButton.click({ timeout: 30000 });
+        await loginPage.usernameInput
+            .or(loginPage.coreUsernameInput)
+            .or(loginPage.keycloakBanner)
+            .first()
+            .waitFor({ state: 'visible', timeout: 15000 })
+            .catch(() => { });
     }
 }
 exports.SettingsPage = SettingsPage;

package/package.json

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