@camunda/e2e-test-suite 0.0.1047 → 0.0.1049

package/dist/pages/SM-8.10/ModelerHomePage.d.ts

@@ -47,6 +47,7 @@ declare class ModelerHomePage {
     clickFormOption(): Promise<void>;
     enterFormName(name: string): Promise<void>;
     private renameViaMoreActions;
+    private waitForEntityCrumb;
     clickProjectBreadcrumb(): Promise<void>;
     clickWorkspaceBreadcrumb(): Promise<void>;
     enterResourceContainer(name?: string): Promise<void>;

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

@@ -356,6 +356,11 @@ class ModelerHomePage {
         // canvas mounts together with the entity crumb, so gate on it rather than
         // on the header, which is present either way.
         await this.page.waitForURL(/\/forms\//, { timeout: 60000 });
+        // The URL flips before the editor mounts, and the app header re-renders as
+        // it does. Renaming in that window finds the kebab but loses the menu it
+        // opens, so wait for the editor canvas first. Soft: on a shell that labels
+        // the canvas differently the retry in renameViaMoreActions still covers us.
+        await this.becameVisible(this.formEditorCanvas, 60000);
         await this.formNameInput
             .or(this.formEditorCanvas)
             .first()
@@ -377,6 +382,12 @@ class ModelerHomePage {
     // menu from the keyboard -- same control, reached the way a keyboard user
     // reaches it, and unaffected by what paints over it.
     //
+    // The header keeps re-rendering for a while after the editor mounts (the
+    // breadcrumb swap, then the license tags arriving in that ml-auto sibling),
+    // and each re-render unmounts the open menu: the nightly trace shows "Rename"
+    // resolving, reporting "element is not stable", then "element was detached
+    // from the DOM". Reopen the menu and try again rather than racing a single
+    // open; the last attempt throws so a genuinely missing menu still fails.
     // A freshly created entity's file data lands after the editor has already
     // painted, and the header re-renders when it does -- which unmounts the open
     // Radix menu mid-click ("element was detached from the DOM, retrying") and
@@ -385,6 +396,7 @@ class ModelerHomePage {
     // test. Escape first: the trigger toggles, so an attempt that left the menu
     // open would otherwise have the next Enter close it again.
     async renameViaMoreActions(name) {
+        await this.waitForEntityCrumb();
         const entityActions = this.moreActionsButton.last();
         // The header keeps settling after the editor paints: the license tags
         // mount into the ml-auto sibling and the breadcrumb label swaps from its
@@ -403,17 +415,31 @@ class ModelerHomePage {
             await this.renameMenuItem.click({ timeout: 15000 });
             await (0, test_1.expect)(this.renameInput).toBeVisible({ timeout: 10000 });
         }).toPass({ timeout: 120000, intervals: [1000, 2000, 5000] });
-        await (0, test_1.expect)(async () => {
-            await this.page.keyboard.press('Escape');
-            await entityActions.focus();
-            await entityActions.press('Enter');
-            await this.renameMenuItem.click({ timeout: 5000 });
-            await (0, test_1.expect)(this.renameInput).toBeVisible({ timeout: 10000 });
-        }).toPass({ timeout: 120000, intervals: [2000] });
         await this.renameInput.fill(name);
         await this.renameSubmitButton.click();
         await (0, test_1.expect)(this.renameInput).toBeHidden({ timeout: 10000 });
     }
+    // The breadcrumb is built up progressively: on a freshly created resource the
+    // container is briefly the deepest crumb and owns the only kebab, and the
+    // entity crumb is appended a render later. Reopening the menu is not enough
+    // on its own -- an attempt that lands inside that window opens the
+    // CONTAINER's menu, so "Rename" there renames the process application
+    // instead of the entity, and the entity crumb's arrival re-renders the
+    // breadcrumb and unmounts the menu mid-click. Wait for the deepest kebab to
+    // stop being the container's. Shells that label the kebab generically
+    // ("More actions") never match a container label, so this is a no-op there.
+    async waitForEntityCrumb() {
+        if (!this.processApplicationName) {
+            return;
+        }
+        const containerActions = `${this.processApplicationName} actions`;
+        await test_1.expect
+            .poll(async () => (await this.moreActionsButton
+            .last()
+            .getAttribute('aria-label')
+            .catch(() => null)) ?? '', { timeout: 30000 })
+            .not.toBe(containerActions);
+    }
     // Kept under its original name because it is what ~10 call sites already
     // mean: "go back to where my resources live". That is now the process
     // application, not the workspace root.

package/dist/tests/SM-8.10/identity-user-flows.spec.js

@@ -76,8 +76,15 @@ SM_8_10_1.test.describe('Identity User Flow Tests', () => {
         });
         if (node_process_1.default.env.IS_OPTIMIZE !== 'false') {
             await SM_8_10_1.test.step('Ensure Optimize is not Accessible', async () => {
-                // Skipped due to bug 60317: https://github.com/camunda/camunda/issues/60317
-                SM_8_10_1.test.skip(true, 'Authorization message not rendering on Optimize forbidden page');
+                // Re-skipped: camunda/camunda#60317 is closed as completed, but this
+                // still reproduces as of 2026-08-31 (run 33382455150) -- and worse
+                // than the original description ("message not rendering"): the
+                // zero-role test user gets the full Optimize dashboard, not just a
+                // missing error message. The Modeler no-access check directly above
+                // this step correctly blocks the same user, so this looks like a
+                // real, unresolved authorization gap specific to Optimize, not a
+                // test setup issue. Flagged for follow-up rather than re-fixed here.
+                SM_8_10_1.test.skip(true, 'Optimize renders full dashboard for a zero-role user instead of denying access -- camunda/camunda#60317 still reproduces');
                 await navigationPage.goToOptimizeWithoutAccess(credentials);
                 await (0, test_1.expect)(page.getByText('User has no authorization to access Optimize. Please check your Identity configuration')).toBeVisible({
                     timeout: 60000,

package/package.json

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