@camunda/e2e-test-suite 0.0.896 → 0.0.898

package/dist/pages/SM-8.10/ModelerCreatePage.js

@@ -164,11 +164,11 @@ class ModelerCreatePage {
         this.clientIdTextbox = page.getByLabel('Client ID');
         this.clientSecretTextbox = page.getByLabel('Client secret');
         this.rememberCredentialsCheckbox = page.getByText('Remember credentials');
-        // Marketplace "Save as copy" imports leave extra copies of the same
-        // connector template in the shared project, each rendered as another
-        // identically-named popup entry but carrying a generated `Template_<id>`.
-        // A name query matches every copy and throws in strict mode, so target the
-        // canonical marketplace template by its stable entry id instead.
+        // A name query matches every project-local copy of this template too
+        // ("Webhook Message Start Event Connector - Copy", left behind by earlier
+        // marketplace imports), so it resolves to several options and clicking
+        // throws in strict mode. Target the bundled template by its stable entry
+        // id, the same way restConnectorOption does.
         this.webhookMessageStartEventConnectorOption = page
             .locator('.djs-popup-results')
             .locator('[data-id="replace.template-io.camunda.connectors.webhook.WebhookConnectorStartMessage.v1"]');
@@ -179,10 +179,9 @@ class ModelerCreatePage {
         this.implementationSection = page.locator('[data-group-id="group-userTaskImplementation"]');
         this.implementationOptions = page.locator('#bio-properties-panel-userTaskImplementation');
         this.assignmentSection = page.locator('[data-group-id="group-assignmentDefinition"]');
-        // 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.
+        // The user-task priority entry renders as <input type="number">, whose ARIA
+        // role is spinbutton, not textbox — so a textbox role query never resolves.
+        // Target it by its stable properties-panel entry id instead.
         this.priorityInput = page.locator('#bio-properties-panel-priorityDefinitionPriority');
         this.appendElementButton = page
             .locator('[class="djs-context-pad open"]')
@@ -1007,6 +1006,9 @@ class ModelerCreatePage {
         }
     }
     async expandAssignmentSection() {
+        // Scoped to assignmentSection already, so the group-id must not be repeated
+        // here: a self-nested selector never matches, the guard always reads
+        // "collapsed" and the click then toggles an open section shut.
         const isExpanded = (await this.assignmentSection
             .locator('.bio-properties-panel-group-header.open')
             .count()) > 0;
@@ -1042,6 +1044,9 @@ class ModelerCreatePage {
             await this.priorityInput.click();
         }
         catch (error) {
+            // Re-expand through the guard rather than clicking the section header
+            // directly — a bare click toggles an already-open section shut and takes
+            // the priority entry out of the DOM for the retry below.
             await this.expandAssignmentSection();
             await this.priorityInput.click({ timeout: 60000 });
         }

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.896",
+  "version": "0.0.898",
   "description": "End-to-end test helpers for Camunda 8",
   "repository": {
     "type": "git",