@camunda/e2e-test-suite 0.0.1037 → 0.0.1039

package/README.md

@@ -415,6 +415,26 @@ See [docs/ci-failure-categories.md](docs/ci-failure-categories.md) for the full
 - **C8 SM with Helm**: Tests are run against the alpha branch of the [camunda-platform-helm repository](https://github.com/camunda/camunda-platform-helm), using SNAPSHOT images for each component. This is peformed with both Elasticsearch and OpenSearch.
 - **C8 Run**: Tests are run against the main branch of the [camunda/camunda repository](https://github.com/camunda/camunda).
 
+## PR-Level vs Nightly Coverage (AlwaysGreen)
+
+When a PR opens in [camunda/camunda](https://github.com/camunda/camunda) or [camunda/connectors](https://github.com/camunda/connectors), AlwaysGreen dispatches a subset of this suite against that PR's build. This is separate from this repo's own [Automatic test runs on PR](#automatic-test-runs-on-pr) above, which cover changes to the test suite itself rather than to the product.
+
+| leg | scope | blocking | runtime |
+| --- | --- | --- | --- |
+| SaaS smoke | `test-setup`, `navigation`, `smoke-tests` | yes | 9–12 min |
+| SaaS full | remaining specs (minus exclusions below) | no, until Nov 2026 | ~40–48 min |
+| SM smoke | smoke suite | yes | — |
+| SM full | full suite | no | — |
+
+**Excluded from PR level entirely — nightly only.** Third-party model-endpoint specs bill an external provider on every run they're included in, so they stay out of the PR-blocking path:
+
+- By spec file: `agentic-ai-user-flows.spec.ts`, `idp-user-flows.spec.ts`, `aws-connectors-user-flows.spec.ts` (AWS Bedrock, AgentCore, Vertex, Azure OpenAI)
+- By tag `@ai-external`: the AI-generated-form tests inside `web-modeler-user-flows.spec.ts` (`Form.js Integration with User Task and AI Generated Form`, `Form.js Integration with AI generated Start form`)
+
+**Kept in at PR level despite touching external systems:** Connector Secrets tests (reads from our own AWS/GCP secret managers — no model endpoint, no meaningful per-run cost) and MCP tests (run against our own cluster — no cost).
+
+See [AlwaysGreen Iteration 2 - Alpha 5: Coverage & Optimisation](https://github.com/camunda/team-test-automation/issues/78) for the full rationale and current SaaS/SM stability data behind these boundaries.
+
 ## Test Suite Structure
 
 The test suite is organized using the Page Object Model design pattern, where each test file contains test scenarios related to a specific component or feature of the Camunda C8 product stack. Additionally, it leverages separate page objects for each web page or component being tested.

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

@@ -155,6 +155,7 @@ declare class ModelerCreatePage {
     clickDiagramBreadcrumb(): Promise<void>;
     clickEditDiagramNameButton(): Promise<void>;
     enterDiagramName(name: string): Promise<void>;
+    private diagramNameEditorOpen;
     clickVariableInput(): Promise<void>;
     fillVariableInput(variable: string): Promise<void>;
     clickEmbedFormButton(): Promise<void>;

package/dist/pages/8.10/ModelerCreatePage.js

@@ -799,25 +799,42 @@ class ModelerCreatePage {
     async enterDiagramName(name) {
         const maxAttempts = 3;
         for (let attempt = 0; attempt < maxAttempts; attempt++) {
-            if (attempt > 0) {
-                await this.clickDiagramBreadcrumb();
-                await this.clickEditDiagramNameButton();
-            }
-            await this.diagramNameInput.fill(name, { timeout: 90000 });
-            await this.diagramNameInput.press('Enter', { timeout: 90000 });
             try {
+                // Creating the diagram does not reliably leave the name editor open --
+                // hub opens the editor on the breadcrumb, and a slow canvas render
+                // lands on a closed one. The input therefore has to be opened on the
+                // FIRST attempt too, not only on a retry: reaching for it blind burnt
+                // the whole 90s fill timeout and threw straight out of this loop, so
+                // the reopen below (which exists for exactly this) never ran.
+                // clickEditDiagramNameButton() reopens the breadcrumb menu itself when
+                // it is closed, so it covers both the first attempt and a retry.
+                if (!(await this.diagramNameEditorOpen())) {
+                    await this.clickEditDiagramNameButton();
+                }
+                // 20s rather than 90s: the editor is proven open at this point, so the
+                // long budget only delayed the retry that actually recovers -- and at
+                // 90s x 2 x 3 attempts this loop could outlive the 12min test timeout,
+                // losing the artifacts that explain the failure.
+                await this.diagramNameInput.fill(name, { timeout: 20000 });
+                await this.diagramNameInput.press('Enter', { timeout: 20000 });
                 await this.diagramNameBreadcrumb(name).waitFor({
                     state: 'visible',
                     timeout: 30000,
                 });
                 return;
             }
-            catch {
-                console.warn(`Diagram rename to "${name}" did not commit on attempt ${attempt + 1}.`);
+            catch (error) {
+                console.warn(`Diagram rename to "${name}" did not commit on attempt ${attempt + 1}: ${error instanceof Error ? error.message : error}`);
             }
         }
         throw new Error(`Diagram name was not set to "${name}".`);
     }
+    async diagramNameEditorOpen() {
+        return this.diagramNameInput
+            .waitFor({ state: 'visible', timeout: 5000 })
+            .then(() => true)
+            .catch(() => false);
+    }
     async clickVariableInput() {
         await this.variableInput.click({ timeout: 60000 });
     }

package/dist/pages/8.10/ModelerHomePage.js

@@ -477,6 +477,16 @@ class ModelerHomePage {
                 await this.clickMessageBanner();
             },
             postAction: async () => {
+                // The project tile only renders on the Modeler home page. A failure
+                // that leaves the browser inside the project makes the tile unreachable
+                // by construction, so reloading the same URL cannot help and every
+                // remaining attempt just waits out its 60s visibility timeout before
+                // the helper throws. Step back out to home first.
+                const tileVisible = await this.becameVisible(this.crossComponentProjectFolder, 2000);
+                if (!tileVisible &&
+                    (await this.becameVisible(this.homeBreadcrumb, 5000))) {
+                    await this.homeBreadcrumb.click({ timeout: 15000 });
+                }
                 await this.page.reload();
                 await this.page.waitForLoadState('domcontentloaded');
             },

package/dist/pages/8.10/ProcessApplicationPage.js

@@ -86,10 +86,17 @@ class ProcessApplicationPage {
             exact: true,
         });
     }
-    // Either the folder explorer or the breadcrumb proves we are on the process
-    // application page; .first() because both are present once it has rendered.
+    // Only the breadcrumb proves we are on the process application page. The
+    // folder explorer does NOT: hub renders a `region[name="Folder explorer"]` on
+    // the enclosing PROJECT page too (trace snapshots on a
+    // `...--cross-component-test-project` URL carry one), so accepting it let
+    // this resolve on the project page whenever creation had not actually landed.
+    // ModelerHomePage then remembered the project URL as the container URL and
+    // every later navigation went back to the project page, where the
+    // container's `[data-test="diagram-dropdown"]` create menu does not exist --
+    // surfacing 60s later as `element(s) not found` on an unrelated step.
     pageReady() {
-        return this.folderExplorer.or(this.breadcrumb).first();
+        return this.breadcrumb;
     }
     async waitForProcessApplication(timeout = 90000) {
         await (0, test_1.expect)(this.pageReady()).toBeVisible({ timeout });

package/package.json

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