@camunda/e2e-test-suite 0.0.753 → 0.0.755

package/dist/pages/8.7/ModelerHomePage.d.ts

@@ -1,6 +1,5 @@
 import { Page, Locator } from '@playwright/test';
 import { LoginPage } from './LoginPage';
-import { AppsPage } from './AppsPage';
 declare class ModelerHomePage {
     private defaultFolderName;
     private page;
@@ -55,15 +54,23 @@ declare class ModelerHomePage {
     assertFormBreadcrumbVisible(formName: string): Promise<void>;
     /**
      * Handles navigation after clicking an invitation link in email.
-     * The invitation link may auto-authenticate the second user and land them in
-     * the correct org's Modeler. If the Modeler banner is visible, navigate to
-     * the Modeler home within the same org context — clearing cookies and
-     * re-logging in via the app switcher lands in the user's personal org where
-     * the shared project is not listed.
-     * If auto-authentication did not occur (page ended up on Auth0), falls back
-     * to the explicit login path.
+     *
+     * The invited user follows the link while logged out, so the invitation flow
+     * presents the Auth0 login. Completing the login ON the invitation flow lets
+     * SaaS accept the invite and land the user directly in the SHARED org's
+     * Modeler, where the shared project is listed.
+     *
+     * We deliberately do NOT clear cookies and re-login via the app switcher:
+     * that path authenticates into the user's PERSONAL org, where the shared
+     * project does not exist and the folder can never appear — the previous
+     * fallback raced a 15s window and, whenever the (normal) login + invite-accept
+     * redirect chain took longer, dropped into that personal-org path and hung.
+     *
+     * If the link auto-authenticated (the banner is already up), no login is
+     * needed. The redirect chain routinely takes longer than a few seconds, so
+     * wait generously for the banner instead of racing a short window.
      */
-    navigateAfterInvitationLink(loginPage: LoginPage, appsPage: AppsPage, credentials: {
+    navigateAfterInvitationLink(loginPage: LoginPage, credentials: {
         username: string;
         password: string;
     }): Promise<void>;

package/dist/pages/8.7/ModelerHomePage.js

@@ -4,7 +4,6 @@ exports.ModelerHomePage = void 0;
 const test_1 = require("@playwright/test");
 const sleep_1 = require("../../utils/sleep");
 const clickLocatorWithRetry_1 = require("../../utils/assertionHelpers/clickLocatorWithRetry");
-const UtilitiesPage_1 = require("./UtilitiesPage");
 class ModelerHomePage {
     defaultFolderName = 'Cross Component Test Project';
     page;
@@ -276,34 +275,44 @@ class ModelerHomePage {
     }
     /**
      * Handles navigation after clicking an invitation link in email.
-     * The invitation link may auto-authenticate the second user and land them in
-     * the correct org's Modeler. If the Modeler banner is visible, navigate to
-     * the Modeler home within the same org context — clearing cookies and
-     * re-logging in via the app switcher lands in the user's personal org where
-     * the shared project is not listed.
-     * If auto-authentication did not occur (page ended up on Auth0), falls back
-     * to the explicit login path.
+     *
+     * The invited user follows the link while logged out, so the invitation flow
+     * presents the Auth0 login. Completing the login ON the invitation flow lets
+     * SaaS accept the invite and land the user directly in the SHARED org's
+     * Modeler, where the shared project is listed.
+     *
+     * We deliberately do NOT clear cookies and re-login via the app switcher:
+     * that path authenticates into the user's PERSONAL org, where the shared
+     * project does not exist and the folder can never appear — the previous
+     * fallback raced a 15s window and, whenever the (normal) login + invite-accept
+     * redirect chain took longer, dropped into that personal-org path and hung.
+     *
+     * If the link auto-authenticated (the banner is already up), no login is
+     * needed. The redirect chain routinely takes longer than a few seconds, so
+     * wait generously for the banner instead of racing a short window.
      */
-    async navigateAfterInvitationLink(loginPage, appsPage, credentials) {
-        const autoAuthenticated = await this.modelerPageBanner
-            .waitFor({ state: 'visible', timeout: 15000 })
+    async navigateAfterInvitationLink(loginPage, credentials) {
+        // If the invitation flow shows the Auth0 login, authenticate in place so
+        // the invite is accepted in the shared-org context. If it doesn't appear,
+        // the link already auto-authenticated us and we skip straight to the banner.
+        const onLogin = await loginPage.usernameInput
+            .waitFor({ state: 'visible', timeout: 60000 })
             .then(() => true)
             .catch(() => false);
-        if (autoAuthenticated) {
-            try {
-                await this.clickHomeBreadcrumb();
-            }
-            catch {
-                // Already on the Modeler home page
-            }
+        if (onLogin) {
+            await loginPage.fillUsername(credentials.username);
+            await loginPage.clickContinueButton();
+            await loginPage.fillPassword(credentials.password);
+            await loginPage.clickLoginButton();
         }
-        else {
-            await this.page.context().clearCookies();
-            await (0, UtilitiesPage_1.loginWithRetry)(this.page, loginPage, credentials, 1000, 3, true);
-            await appsPage.clickCamundaApps();
-            await appsPage.clickModeler();
+        await (0, test_1.expect)(this.modelerPageBanner).toBeVisible({ timeout: 180000 });
+        try {
+            await this.clickHomeBreadcrumb();
+        }
+        catch {
+            // Already on the Modeler home page
         }
-        await (0, test_1.expect)(this.modelerPageBanner).toBeVisible({ timeout: 120000 });
+        await (0, test_1.expect)(this.modelerPageBanner).toBeVisible({ timeout: 30000 });
     }
 }
 exports.ModelerHomePage = ModelerHomePage;

package/dist/pages/8.7/UtilitiesPage.d.ts

@@ -29,6 +29,7 @@ export declare function runMultipleProcesses(clusterName: string, page: Page, mo
     numberOfProcesses?: number;
     processName?: string;
     uploadFromFile?: string;
+    settleBetween?: (processId: string) => Promise<void>;
 }): Promise<void>;
 export declare function runProcess(clusterName: string, page: Page, modelerHomePage: ModelerHomePage, modelerCreatePage: ModelerCreatePage, processName: string, processId?: string, uploadFromFile?: string): Promise<void>;
 export declare function modelDiagramFromFile(page: Page, modelerHomePage: ModelerHomePage, modelerCreatePage: ModelerCreatePage, processName: string, fileName?: string, nrOfRenamedUserTasks?: number, taskName?: string): Promise<void>;

package/dist/pages/8.7/UtilitiesPage.js

@@ -219,10 +219,20 @@ async function completeTaskWithRetry(taskPanelPage, taskDetailsPage, taskName, t
 }
 exports.completeTaskWithRetry = completeTaskWithRetry;
 async function runMultipleProcesses(clusterName, page, modelerHomePage, modelerCreatePage, options) {
-    const { processName = 'Camunda_User_Task', numberOfProcesses = 2, uploadFromFile = '', } = options || {};
+    const { processName = 'Camunda_User_Task', numberOfProcesses = 2, uploadFromFile = '', settleBetween, } = options || {};
     for (let i = 1; i <= numberOfProcesses; i++) {
         await runProcess(clusterName, page, modelerHomePage, modelerCreatePage, processName + i, processName + i, uploadFromFile);
         await modelerHomePage.clickProjectBreadcrumb();
+        // When RBA is enabled, deploying a process auto-provisions a resource
+        // authorization for the deployer keyed on the process definition id. The
+        // identity service writes that grant with a read-modify-write, so deploying
+        // the next process before this grant lands clobbers it (lost update) and it
+        // is permanently missing. When a settleBetween hook is supplied, wait for
+        // the just-deployed grant to be durably provisioned before the next deploy —
+        // a deterministic wait, not a fixed sleep.
+        if (settleBetween && i < numberOfProcesses) {
+            await settleBetween(processName + i);
+        }
     }
 }
 exports.runMultipleProcesses = runMultipleProcesses;

package/dist/tests/8.7/rba-enabled-user-flows.spec.js

@@ -236,6 +236,31 @@ _8_7_1.test.describe('RBA Enabled User Flows Test', () => {
             await (0, UtilitiesPage_1.runMultipleProcesses)(clusterName, page, modelerHomePage, modelerCreatePage, {
                 processName: processName,
                 uploadFromFile: 'Camunda_Simple_User_Task_1',
+                // RBA is enabled before this deploy, so each process start
+                // auto-provisions the deployer's resource authorization via a
+                // read-modify-write. Deploying the second process before the first
+                // grant lands clobbers it (lost update), permanently dropping one of
+                // the two process ids — which no downstream wait can recover (see
+                // authorizedResourcesAssertion). Before deploying the next process,
+                // wait for the just-deployed grant to appear in Console, then return
+                // to the project. Deterministic, unlike a fixed sleep.
+                settleBetween: async (processId) => {
+                    await appsPage.clickCamundaApps();
+                    await appsPage.clickConsoleLink();
+                    await homePage.clickOrganization();
+                    await consoleOrganizationsPage.clickUsersTab();
+                    await consoleOrganizationsPage.clickMainUser(mainUser.username);
+                    await consoleOrganizationsPage.clickAuthorizations();
+                    await consoleOrganizationsPage.authorizedResourcesAssertion([
+                        processId,
+                    ]);
+                    await appsPage.clickCamundaApps();
+                    await appsPage.clickModeler();
+                    await (0, test_1.expect)(modelerHomePage.modelerPageBanner).toBeVisible({
+                        timeout: 120000,
+                    });
+                    await modelerHomePage.clickCrossComponentProjectFolder();
+                },
             });
             await (0, sleep_1.sleep)(60000);
         });

package/dist/tests/8.7/web-modeler-user-flows.spec.js

@@ -514,12 +514,17 @@ _8_7_1.test.describe('Web Modeler User Flow Tests', () => {
         });
         await _8_7_1.test.step('Log in with Second User and Navigate to Cross Component Test project as Collaborator', async () => {
             await (0, UtilitiesPage_1.clickInvitationLinkInEmail)(page, id);
-            await (0, sleep_1.sleep)(60000);
-            await modelerHomePage.navigateAfterInvitationLink(loginPage, appsPage, {
+            await modelerHomePage.navigateAfterInvitationLink(loginPage, {
                 username: emailAddress,
                 password: password,
             });
-            await (0, UtilitiesPage_1.assertLocatorVisibleWithRetry)(modelerHomePage, modelerHomePage.crossComponentProjectFolder, 'Cross Component Test Project', 90000, 20);
+            // navigateAfterInvitationLink lands the invited user in the SHARED org's
+            // Modeler home (it logs in on the invitation flow rather than
+            // re-authenticating into the personal org), so the shared project is
+            // present. Assert its visibility directly — no session-breaking reload.
+            await (0, test_1.expect)(modelerHomePage.crossComponentProjectFolder).toBeVisible({
+                timeout: 120000,
+            });
         });
         await _8_7_1.test.step('Log out from Second User', async () => {
             await settingsPage.clickOpenSettingsButton();

package/package.json

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