@camunda/e2e-test-suite 0.0.1232 → 0.0.1233

package/dist/pages/8.10/ModelerCreatePage.d.ts

@@ -225,6 +225,7 @@ declare class ModelerCreatePage {
     embedForm(formName: string): Promise<void>;
     openDetailsPanelIfCollapsed(): Promise<void>;
     fillStartEventVariablesForDocHandling(zeebeUrl: string, zeebeClientId: string, zeebeClientSecret: string): Promise<void>;
+    private expandOutputMappingEntry;
     fillZeebeClientId(clientId: string): Promise<void>;
     fillZeebeSecretValue(zeebeSecret: string): Promise<void>;
     fillZeebeRestValue(zeebeUrl: string): Promise<void>;

package/dist/pages/8.10/ModelerCreatePage.js

@@ -1856,11 +1856,35 @@ class ModelerCreatePage {
         await this.fillZeebeClientId(zeebeClientId);
         await (0, sleep_1.sleep)(1000);
     }
+    // Each Output mapping row is a collapsible properties-panel entry whose
+    // header *toggles* on click, so a single blind click is not idempotent: when
+    // the panel re-renders while the click is in flight — it does, right after
+    // the preceding FEEL editor commits its value — the entry ends up collapsed
+    // again and its editor keeps a zero-size box. That is what reported
+    // `expect(#bio-properties-panel-StartEvent_1-output-2-source div)
+    // .toBeVisible()` timing out with "unexpected value hidden" for a full 60s
+    // while the trace screenshot showed zeebeRestAdress and zeebeSecret open and
+    // zeebeClientId collapsed. Ask for the state instead of assuming it: only
+    // click while the editor is still hidden, and re-check after each click.
+    async expandOutputMappingEntry(header, editor) {
+        const maxAttempts = 5;
+        for (let attempt = 0; attempt < maxAttempts; attempt++) {
+            if (await editor.isVisible().catch(() => false)) {
+                return;
+            }
+            await header.click();
+            const opened = await editor
+                .waitFor({ state: 'visible', timeout: 15000 })
+                .then(() => true)
+                .catch(() => false);
+            if (opened) {
+                return;
+            }
+        }
+        await (0, test_1.expect)(editor).toBeVisible({ timeout: 60000 });
+    }
     async fillZeebeClientId(clientId) {
-        await this.zeebeClientIdVariable.click();
-        await (0, test_1.expect)(this.variableAssignmentValueTextboxThirdVariable).toBeVisible({
-            timeout: 60000,
-        });
+        await this.expandOutputMappingEntry(this.zeebeClientIdVariable, this.variableAssignmentValueTextboxThirdVariable);
         await this.variableAssignmentValueTextboxThirdVariable.click();
         await (0, sleep_1.sleep)(1000);
         await this.variableAssignmentValueTextboxThirdVariable.fill('');
@@ -1868,10 +1892,7 @@ class ModelerCreatePage {
         await (0, test_1.expect)(this.variableAssignmentValueTextboxThirdVariable).toHaveText(clientId);
     }
     async fillZeebeSecretValue(zeebeSecret) {
-        await this.zeebeSecretVariable.click();
-        await (0, test_1.expect)(this.variableAssignmentValueTextboxSecondVariable).toBeVisible({
-            timeout: 60000,
-        });
+        await this.expandOutputMappingEntry(this.zeebeSecretVariable, this.variableAssignmentValueTextboxSecondVariable);
         await this.variableAssignmentValueTextboxSecondVariable.click();
         await (0, sleep_1.sleep)(1000);
         await this.variableAssignmentValueTextboxSecondVariable.fill('');
@@ -1879,10 +1900,7 @@ class ModelerCreatePage {
         await (0, test_1.expect)(this.variableAssignmentValueTextboxSecondVariable).toHaveText(zeebeSecret);
     }
     async fillZeebeRestValue(zeebeUrl) {
-        await this.zeebeRestAddressVariable.click();
-        await (0, test_1.expect)(this.variableAssignmentValueTextbox).toBeVisible({
-            timeout: 60000,
-        });
+        await this.expandOutputMappingEntry(this.zeebeRestAddressVariable, this.variableAssignmentValueTextbox);
         await this.variableAssignmentValueTextbox.click();
         await (0, sleep_1.sleep)(1000);
         await this.variableAssignmentValueTextbox.fill('');

package/dist/pages/8.10/OptimizeCollectionsPage.js

@@ -33,8 +33,10 @@ class OptimizeCollectionsPage {
             .or(page.getByRole('button', { name: 'Collection', exact: true }));
         this.modalCloseButton = page.locator('button').filter({ hasText: /^Close$/ });
         this.processReport = page.getByText('Process Report').first();
+        // See OptimizeHomePage: Optimize's Design System navigation moved this
+        // link out of the top banner into the left sidebar.
         this.collectionsLink = page
-            .getByRole('banner')
+            .getByRole('navigation', { name: 'Main navigation' })
             .getByRole('link', { name: 'Collections' });
         this.collectionNameInput = page
             .getByRole('dialog')

package/dist/pages/8.10/OptimizeDashboardPage.js

@@ -7,7 +7,13 @@ class OptimizeDashboardPage {
     filterTable;
     constructor(page) {
         this.page = page;
-        this.filterTable = page.getByPlaceholder('Filter table');
+        // Optimize's Design System EntityList replaced the Carbon table toolbar
+        // search (placeholder "Filter table") with a plain input whose placeholder
+        // is the `home.search.name` translation, "Search for name...". With the
+        // old placeholder `clickFilterTable` waited out its 120s on every one of
+        // the five attempts, which is what reported "Process link in Optimize
+        // assertion failed after 5 attempts".
+        this.filterTable = page.getByPlaceholder(/Search for name/i);
     }
     async clickFilterTable() {
         await this.filterTable.click({ timeout: 120000 });

package/dist/pages/8.10/OptimizeHomePage.js

@@ -31,9 +31,19 @@ class OptimizeHomePage {
     filterTableInput;
     constructor(page) {
         this.page = page;
-        this.filterTableInput = page.getByPlaceholder('Filter table');
+        // Optimize's Design System EntityList replaced the Carbon table toolbar
+        // search (placeholder "Filter table") with a plain input whose placeholder
+        // is the `home.search.name` translation, "Search for name...". Matching on
+        // the old placeholder resolved to nothing, so `filterTableToProcess` below
+        // silently fell through and every polling round asserted against the
+        // unfiltered — and now paginated — definition table.
+        this.filterTableInput = page.getByPlaceholder(/Search for name/i);
+        // The same navigation rollout moved Dashboards/Collections out of the top
+        // banner into a left sidebar (`<nav aria-label="Main navigation">`), and
+        // the legacy banner navigation was deleted outright, so a banner-scoped
+        // link can never resolve again.
         this.collectionsLink = page
-            .getByRole('banner')
+            .getByRole('navigation', { name: 'Main navigation' })
             .getByRole('link', { name: 'Collections' });
         this.dashboardLink = page.getByRole('link', { name: 'Dashboards' });
         this.modalCloseButton = page.locator('button').filter({ hasText: /^Close$/ });

package/dist/resources/agentic_ai/ai-agent-chat-with-tools_gemini_vertex.bpmn

@@ -43,7 +43,7 @@
             source="You are a helpful, generic chat agent which can answer a wide amount of questions based on your knowledge and an optional set of available tools.

If tools are provided, you should prefer them instead of guessing an answer. You can call the same tool multiple times by providing different input values. Don't guess any tools which were not explicitely configured. If no tool matches the request, try to generate an answer. If you're not able to find a good answer, return with a message stating why you're not able to.

If you are prompted to interact with a person, never guess contact details, but use available user/person lookup tools instead and return with an error if you're not able to look up appropriate data.

Thinking, step by step, before you execute your tools, you think using the template `<thinking><context></context><reflection></reflection></thinking>`"
             target="data.systemPrompt.prompt" />
           <zeebe:input
-            source="=&#34;Generate a single sentence in the following exact format, using Paris, France as the city and country:&#10;&#10;The current date and time in {City, Country}, is approximately {h:mm AM/PM} on {Month day, year}.&#10;&#10;But only with the sentence/format as above, nothing else&#34;"
+            source="=&#34;Generate a single sentence in the following exact format, always using a new random city and country each time:&#10;&#10;The current date and time in {City, Country}, is approximately {h:mm AM/PM} on {Month day, year}.&#10;&#10;But only with the sentence/format as above, nothing else&#34;"
             target="data.userPrompt.prompt" />
           <zeebe:input
             source="=if (is defined(followUpInput) or is defined(followUpDocuments)) then followUpDocuments else inputDocuments"

package/package.json

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

package/resources/agentic_ai/ai-agent-chat-with-tools_gemini_vertex.bpmn

@@ -43,7 +43,7 @@
             source="You are a helpful, generic chat agent which can answer a wide amount of questions based on your knowledge and an optional set of available tools.

If tools are provided, you should prefer them instead of guessing an answer. You can call the same tool multiple times by providing different input values. Don't guess any tools which were not explicitely configured. If no tool matches the request, try to generate an answer. If you're not able to find a good answer, return with a message stating why you're not able to.

If you are prompted to interact with a person, never guess contact details, but use available user/person lookup tools instead and return with an error if you're not able to look up appropriate data.

Thinking, step by step, before you execute your tools, you think using the template `<thinking><context></context><reflection></reflection></thinking>`"
             target="data.systemPrompt.prompt" />
           <zeebe:input
-            source="=&#34;Generate a single sentence in the following exact format, using Paris, France as the city and country:&#10;&#10;The current date and time in {City, Country}, is approximately {h:mm AM/PM} on {Month day, year}.&#10;&#10;But only with the sentence/format as above, nothing else&#34;"
+            source="=&#34;Generate a single sentence in the following exact format, always using a new random city and country each time:&#10;&#10;The current date and time in {City, Country}, is approximately {h:mm AM/PM} on {Month day, year}.&#10;&#10;But only with the sentence/format as above, nothing else&#34;"
             target="data.userPrompt.prompt" />
           <zeebe:input
             source="=if (is defined(followUpInput) or is defined(followUpDocuments)) then followUpDocuments else inputDocuments"