@camunda/e2e-test-suite 0.0.1018 → 0.0.1020

package/dist/pages/8.10/AuditLogPage.js

@@ -38,6 +38,11 @@ class AuditLogPage {
         await (0, test_1.expect)(checkbox).toBeChecked();
         return true;
     }
+    // Not used by cluster setup: Console re-seeds this panel's checkbox state
+    // from the cluster on every background refresh, so selections made before
+    // "Update" is pressed can be dropped and only some categories get saved. Use
+    // ensureClientAuditLoggingViaApi (utils/consoleApiHelpers) to configure a
+    // cluster; drive this only when the UI itself is what is under test.
     async enableClientOperationLogging() {
         const categories = [
             'Administration',

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

@@ -23,6 +23,7 @@ declare class ModelerHomePage {
     readonly uploadFilesButton: Locator;
     readonly messageBanner: Locator;
     readonly idpTemplateOption: Locator;
+    readonly idpEmptyStateButton: Locator;
     readonly idpApplicationNameInput: Locator;
     readonly createIdpApplicationButton: Locator;
     readonly dialog: Locator;
@@ -40,6 +41,7 @@ declare class ModelerHomePage {
     clickProcessDiagram(name: string): Promise<void>;
     clickDiagramTypeDropdown(): Promise<void>;
     clickWorkspaceDiagramTypeDropdown(): Promise<void>;
+    startIdpApplicationCreation(): Promise<void>;
     clickBpmnTemplateOption(): Promise<void>;
     clickFormOption(): Promise<void>;
     enterFormName(name: string): Promise<void>;

package/dist/pages/8.9/ModelerHomePage.js

@@ -40,6 +40,7 @@ class ModelerHomePage {
     uploadFilesButton;
     messageBanner;
     idpTemplateOption;
+    idpEmptyStateButton;
     idpApplicationNameInput;
     createIdpApplicationButton;
     dialog;
@@ -68,6 +69,12 @@ class ModelerHomePage {
         this.idpTemplateOption = page
             .locator('[data-test="create-idp-application"]')
             .getByText('IDP Application');
+        // Empty workspace root: a plain button in hub's EmptyStateActionButtons,
+        // next to the "Create process application" CTA that ProcessApplicationPage
+        // already reaches for. .first() defensively only, matching that locator.
+        this.idpEmptyStateButton = page
+            .getByRole('button', { name: 'Create IDP application' })
+            .first();
         this.diagramTypeDropdown = page.locator('[data-test="diagram-dropdown"]');
         // Matched on the test id alone: hub's design-system variant of the create
         // menu renders "BPMN diagram" (lowercase d), so a text filter breaks the
@@ -189,6 +196,26 @@ class ModelerHomePage {
         });
         await this.diagramTypeDropdown.click();
     }
+    // Starts an IDP application from the workspace root. Which control exists
+    // there depends on whether the workspace holds anything: hub's EntityTable
+    // renders either the toolbar -- whose "Create new" menu carries the IDP item
+    // -- or the empty state, whose CTA is a plain button, never both. A fresh
+    // org lands on the empty state, so waiting on the menu alone finds no
+    // element at all. Race both and use whichever rendered; same shape as
+    // clickCreateProcessApplication, which already covers this for the sibling
+    // resource type.
+    async startIdpApplicationCreation() {
+        const rootLoaded = await this.becameVisible(this.idpEmptyStateButton.or(this.diagramTypeDropdown).first(), 60000);
+        if (!rootLoaded) {
+            await this.page.reload();
+        }
+        if (await this.becameVisible(this.idpEmptyStateButton, 5000)) {
+            await this.idpEmptyStateButton.click({ timeout: 60000 });
+            return;
+        }
+        await this.clickWorkspaceDiagramTypeDropdown();
+        await this.clickIdpApplicationTemplateOption();
+    }
     async clickBpmnTemplateOption() {
         await (0, test_1.expect)(this.bpmnTemplateOption).toBeVisible({
             timeout: 15000,

package/dist/pages/8.9/OCIdentityRolesPage.js

@@ -4,6 +4,7 @@ exports.OCIdentityRolesPage = void 0;
 const test_1 = require("@playwright/test");
 const expectLocatorWithRetry_1 = require("../../utils/assertionHelpers/expectLocatorWithRetry");
 const expectLocatorWithPagination_1 = require("../../utils/assertionHelpers/expectLocatorWithPagination");
+const submitModalWithRetry_1 = require("../../utils/assertionHelpers/submitModalWithRetry");
 class OCIdentityRolesPage {
     page;
     selectResourceTypeTab;
@@ -128,8 +129,12 @@ class OCIdentityRolesPage {
         await (0, test_1.expect)(this.createRoleModal).toBeVisible({ timeout: 30000 });
         await this.createIdField.fill(role.id);
         await this.createNameField.fill(role.name);
-        await this.createRoleModalCreateButton.click();
-        await (0, test_1.expect)(this.createRoleModal).not.toBeVisible({ timeout: 30000 });
+        // POST /v2/roles intermittently answers 503 UNAVAILABLE ("connection error
+        // with one of the brokers") while a freshly created org's orchestration
+        // cluster settles. The modal then stays open with the form still valid, so
+        // re-submitting recovers; the close assertion itself is unchanged, and a
+        // persistent failure still fails the test.
+        await (0, submitModalWithRetry_1.submitModalWithRetry)(this.createRoleModalCreateButton, this.createRoleModal, { closeTimeout: 30000 });
         await (0, expectLocatorWithPagination_1.expectLocatorWithPagination)(this.page, this.rolesList
             .getByRole('cell', {
             name: role.name,

package/dist/tests/8.10/test-setup.spec.js

@@ -55,7 +55,7 @@ _8_10_1.test.describe('Cluster Setup Tests', () => {
             await clusterSecretsPage.createSetOfSecrets(clusterName, connectorSecrets_1.bedrockCodeInterpreterSecretsValues);
         }
     });
-    (0, _8_10_1.test)('Create Agentic Orchestration Cluster', async ({ page, loginPage, homePage, clusterPage, clusterDetailsPage, clusterSecretsPage, auditLogPage, }, testInfo) => {
+    (0, _8_10_1.test)('Create Agentic Orchestration Cluster', async ({ page, loginPage, homePage, clusterPage, clusterDetailsPage, clusterSecretsPage, }, testInfo) => {
         _8_10_1.test.skip(process.env.IS_PROD === 'true', 'Skipping test because not required on PROD test org');
         _8_10_1.test.skip(process.env.IS_AG === 'true', 'Skipping test because not required when IS_AG is true');
         _8_10_1.test.slow();
@@ -69,8 +69,9 @@ _8_10_1.test.describe('Cluster Setup Tests', () => {
         await homePage.clickClusters();
         await clusterPage.clickClusterLink(clusterName);
         await clusterDetailsPage.assertComponentsHealth();
-        await auditLogPage.clickAuditLogTab();
-        await auditLogPage.enableClientOperationLogging();
+        // Must happen before the MCP toggle: the restart that toggle triggers is
+        // what makes the new audit-log configuration live on the cluster.
+        await (0, consoleApiHelpers_1.ensureClientAuditLoggingViaApi)(page, clusterUuid);
         await clusterDetailsPage.clickSettingsTab();
         await clusterDetailsPage.checkMcpSupportToggle();
         // Enabling MCP support restarts the cluster (Console shows a "Restart

package/dist/tests/8.9/idp-user-flows.spec.js

@@ -94,10 +94,11 @@ _8_9_1.test.describe('IDP User Flow Tests', () => {
                     await modelerHomePage.clickCrossComponentProjectFolder();
                 });
                 await _8_9_1.test.step('Add an IDP application to the project', async () => {
-                    // Workspace-level menu: an IDP application can only be created at
-                    // workspace root, never inside a process application.
-                    await modelerHomePage.clickWorkspaceDiagramTypeDropdown();
-                    await modelerHomePage.clickIdpApplicationTemplateOption();
+                    // Workspace level: an IDP application can only be created at
+                    // workspace root, never inside a process application. The control
+                    // there is the empty-state CTA or the "Create new" menu item,
+                    // depending on whether the workspace already holds anything.
+                    await modelerHomePage.startIdpApplicationCreation();
                 });
                 await _8_9_1.test.step('Creates a document extraction template', async () => {
                     await modelerHomePage.enterIdpApplicationName(idpApplicationName);
@@ -168,10 +169,11 @@ _8_9_1.test.describe('IDP User Flow Tests', () => {
                     await modelerHomePage.clickCrossComponentProjectFolder();
                 });
                 await _8_9_1.test.step('Add an IDP application to the project', async () => {
-                    // Workspace-level menu: an IDP application can only be created at
-                    // workspace root, never inside a process application.
-                    await modelerHomePage.clickWorkspaceDiagramTypeDropdown();
-                    await modelerHomePage.clickIdpApplicationTemplateOption();
+                    // Workspace level: an IDP application can only be created at
+                    // workspace root, never inside a process application. The control
+                    // there is the empty-state CTA or the "Create new" menu item,
+                    // depending on whether the workspace already holds anything.
+                    await modelerHomePage.startIdpApplicationCreation();
                 });
                 await _8_9_1.test.step('Creates a document extraction template', async () => {
                     await modelerHomePage.enterIdpApplicationName(idpApplicationName);
@@ -250,10 +252,11 @@ _8_9_1.test.describe('IDP User Flow Tests', () => {
                     await modelerHomePage.clickCrossComponentProjectFolder();
                 });
                 await _8_9_1.test.step('Add an IDP application to the project', async () => {
-                    // Workspace-level menu: an IDP application can only be created at
-                    // workspace root, never inside a process application.
-                    await modelerHomePage.clickWorkspaceDiagramTypeDropdown();
-                    await modelerHomePage.clickIdpApplicationTemplateOption();
+                    // Workspace level: an IDP application can only be created at
+                    // workspace root, never inside a process application. The control
+                    // there is the empty-state CTA or the "Create new" menu item,
+                    // depending on whether the workspace already holds anything.
+                    await modelerHomePage.startIdpApplicationCreation();
                 });
                 await _8_9_1.test.step('Creates a classification template', async () => {
                     await modelerHomePage.enterIdpApplicationName(idpApplicationName);

package/dist/utils/consoleApiHelpers.d.ts

@@ -3,5 +3,6 @@ export declare function deleteClusterViaApi(page: Page, clusterName: string): Pr
 export declare function createClusterViaApi(page: Page, clusterName: string, region?: string, tasklistV2Enabled?: boolean): Promise<string>;
 export declare function ensureClusterViaApi(page: Page, clusterName: string, region?: string, tasklistV2Enabled?: boolean): Promise<string>;
 export declare function ensureTasklistV2Enabled(page: Page, clusterUuid: string): Promise<void>;
+export declare function ensureClientAuditLoggingViaApi(page: Page, clusterUuid: string): Promise<void>;
 export declare function waitForClusterHealthyViaApi(page: Page, clusterUuid: string, timeoutMs?: number): Promise<void>;
 export declare function waitForClusterRestartHealthyViaApi(page: Page, clusterUuid: string, timeoutMs?: number): Promise<void>;

package/dist/utils/consoleApiHelpers.js

@@ -1,6 +1,6 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.waitForClusterRestartHealthyViaApi = exports.waitForClusterHealthyViaApi = exports.ensureTasklistV2Enabled = exports.ensureClusterViaApi = exports.createClusterViaApi = exports.deleteClusterViaApi = void 0;
+exports.waitForClusterRestartHealthyViaApi = exports.waitForClusterHealthyViaApi = exports.ensureClientAuditLoggingViaApi = exports.ensureTasklistV2Enabled = exports.ensureClusterViaApi = exports.createClusterViaApi = exports.deleteClusterViaApi = void 0;
 const test_1 = require("@playwright/test");
 const sleep_1 = require("./sleep");
 const PLAN_TYPE_ID = '574cde5f-54ae-43c1-851a-e6fb4f03423a';
@@ -401,6 +401,42 @@ async function ensureTasklistV2Enabled(page, clusterUuid) {
     }
 }
 exports.ensureTasklistV2Enabled = ensureTasklistV2Enabled;
+// Client operation logging is opt-in: a fresh cluster carries no audit-log
+// config at all, which Console renders as "all user categories, no client
+// categories". The MCP audit-log specs assert on CLIENT-actor PROCESS_INSTANCE
+// entries, and the engine only records those when the DEPLOYED_RESOURCES client
+// category is enabled.
+//
+// Driving the Audit log tab's checkboxes cannot set this reliably: the panel
+// re-seeds its checkbox state from the cluster every time Console refreshes it
+// in the background, silently dropping selections made before "Update" is
+// pressed. The 2026-08-26/27 nightlies persisted only the last category clicked
+// ("USER_TASKS"), so DEPLOYED_RESOURCES stayed off and every SC-AUD spec polled
+// an audit log that would never receive an entry. Call the same endpoint the
+// Update button calls, then read the config back until it is really persisted.
+const AUDIT_LOG_CATEGORIES = ['ADMIN', 'DEPLOYED_RESOURCES', 'USER_TASKS'];
+async function ensureClientAuditLoggingViaApi(page, clusterUuid) {
+    const orgId = getOrgId();
+    const url = `${getConsoleBaseUrl()}/api/orgs/${orgId}/clusters/${clusterUuid}`;
+    const response = await clusterApiRequest(page, 'PATCH', url, {
+        auditLogEnabled: true,
+        auditLogUserCategories: AUDIT_LOG_CATEGORIES,
+        auditLogClientCategories: AUDIT_LOG_CATEGORIES,
+    });
+    if (response.status() !== 200 && response.status() !== 204) {
+        throw new Error(`Failed to enable client audit logging on cluster "${clusterUuid}": ` +
+            `HTTP ${response.status()} - ${await response.text()}`);
+    }
+    await (0, test_1.expect)(async () => {
+        const readBack = await clusterApiRequest(page, 'GET', url);
+        (0, test_1.expect)(readBack.status()).toBe(200);
+        const body = await readBack.json();
+        const auditLog = (body.data ?? body)?.externalMetadata?.auditLog;
+        (0, test_1.expect)(auditLog?.enabled).toBe(true);
+        (0, test_1.expect)([...(auditLog?.clientCategories ?? [])].sort()).toEqual([...AUDIT_LOG_CATEGORIES].sort());
+    }).toPass({ timeout: 120000, intervals: [2000, 5000, 10000] });
+}
+exports.ensureClientAuditLoggingViaApi = ensureClientAuditLoggingViaApi;
 async function waitForClusterHealthyViaApi(page, clusterUuid, timeoutMs = 1500000) {
     const orgId = getOrgId();
     const url = `${getConsoleBaseUrl()}/api/orgs/${orgId}/clusters/${clusterUuid}`;

package/dist/utils/constants.js

@@ -14,14 +14,13 @@ exports.deletionAssertionOptions = {
     intervals: [5000, 10000, 15000, 30000],
     timeout: 60000,
 };
-// Longest options for audit-log assertions: entries land in secondary storage
-// only after the audit config propagates to the exporters, which is markedly
-// slower on freshly-provisioned SaaS clusters. 90s occasionally lapsed before
-// the CLIENT-actor PROCESS_INSTANCE CREATE entry surfaced, then 180s did too
-// (every audit test in the nightly timed out on the same fresh org, including
-// the REST-triggered one, so nothing about the entry itself was wrong — the
-// pipeline simply had not started exporting yet). Poll for 360s, which still
-// leaves headroom inside the 12-minute test timeout after the ~60s beforeAll.
+// Longest options for audit-log assertions. Measured on the nightly, a
+// CLIENT-actor PROCESS_INSTANCE CREATE entry surfaces within ~10s whenever the
+// cluster has the DEPLOYED_RESOURCES client category enabled — the earlier 90s
+// and 180s budgets were raised against runs where that category was never
+// persisted at all, so no budget could have helped. Keep a generous 360s so a
+// genuinely slow export still passes; it fits inside the 12-minute test timeout
+// after the ~60s beforeAll.
 exports.auditLogAssertionOptions = {
     intervals: [5000, 10000, 15000, 20000, 30000],
     timeout: 360000,

package/package.json

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