@camunda/e2e-test-suite 0.0.1036 → 0.0.1038

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.8/ModelerHomePage.d.ts

@@ -13,6 +13,7 @@ declare class ModelerHomePage {
     readonly diagramTypeDropdown: Locator;
     readonly bpmnTemplateOption: Locator;
     readonly formTemplateOption: Locator;
+    readonly diagramPropertiesPanel: Locator;
     readonly projectBreadcrumb: Locator;
     readonly workspaceBreadcrumb: Locator;
     readonly openOrganizationsButton: Locator;

package/dist/pages/8.8/ModelerHomePage.js

@@ -30,6 +30,9 @@ class ModelerHomePage {
     diagramTypeDropdown;
     bpmnTemplateOption;
     formTemplateOption;
+    // Same group the spec asserts on ModelerCreatePage: it is what proves the
+    // BPMN editor opened, and clickBpmnTemplateOption() has to know that here.
+    diagramPropertiesPanel;
     projectBreadcrumb;
     workspaceBreadcrumb;
     openOrganizationsButton;
@@ -77,6 +80,7 @@ class ModelerHomePage {
         // day that variant ships.
         this.bpmnTemplateOption = page.locator('[data-test="create-bpmn-diagram"]');
         this.formTemplateOption = page.locator('[data-test="create-form"]');
+        this.diagramPropertiesPanel = page.locator('[data-group-id="group-general"]');
         this.projectBreadcrumb = page.locator('[data-test="breadcrumb-project"]');
         // Kept separate from projectBreadcrumb, which now means "the container my
         // resources live in". When hub's workspaces terminology flag flips,
@@ -292,8 +296,28 @@ class ModelerHomePage {
             }
         }
     }
+    // Confirms the editor actually opened instead of trusting the click. The
+    // create menu can close without navigating -- hub re-renders it while the
+    // container's resource list settles -- and nothing here noticed: the browser
+    // stayed on the process application page and the failure surfaced 60s later
+    // as `[data-group-id="group-general"]` / `element(s) not found` on the
+    // spec's own properties-panel assertion, which reads as an editor bug rather
+    // than a lost click. Re-open the menu and click again when the editor is not
+    // there; the 60s probe first means a merely slow canvas render is waited
+    // out rather than creating a second diagram.
     async clickBpmnTemplateOption() {
-        await this.bpmnTemplateOption.click({ timeout: 120000 });
+        await (0, test_1.expect)(async () => {
+            if (await this.becameVisible(this.diagramPropertiesPanel, 1000)) {
+                return;
+            }
+            if (!(await this.becameVisible(this.bpmnTemplateOption, 5000))) {
+                await this.clickDiagramTypeDropdown();
+            }
+            // 30s rather than the old 120s: the option is proven visible above, so a
+            // longer click budget only ate the time the retry below needs.
+            await this.bpmnTemplateOption.click({ timeout: 30000 });
+            await (0, test_1.expect)(this.diagramPropertiesPanel).toBeVisible({ timeout: 60000 });
+        }).toPass({ timeout: 240000, intervals: [1000, 2000, 5000] });
     }
     async clickFormOption() {
         await this.formTemplateOption.click();
@@ -499,6 +523,17 @@ 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 -- createForm's recovery
+                // path below reloads and calls straight back in here -- 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/package.json

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