@camunda/e2e-test-suite 0.0.1460 → 0.0.1461

package/README.md

@@ -498,9 +498,13 @@ By following this convention, we ensure **clarity, consistency, and alignment wi
 
 | Directory Name                | Meaning                                                                                              |
 | ----------------------------- | ---------------------------------------------------------------------------------------------------- |
+| `camunda-platform-8.11-latest` | Runs SM tests against the latest 8.11 SNAPSHOT                                                      |
+| `camunda-platform-8.10-latest` | Runs SM tests against the latest 8.10 SNAPSHOT                                                      |
 | `camunda-platform-8.9-latest` | Runs SM tests against the latest 8.9 SNAPSHOT                                                        |
 | `camunda-platform-8.8-latest` | Runs SM tests against the latest 8.8 SNAPSHOT                                                        |
 | `camunda-platform-8.7-latest` | Runs SM tests against the latest 8.7 SNAPSHOT                                                        |
+| `camunda-platform-8.11`       | Runs SM tests against the 8.11 directory. This is where the `release-candidate-8.11` branch is located |
+| `camunda-platform-8.10`       | Runs SM tests against the 8.10 directory. This is where the `release-candidate-8.10` branch is located |
 | `camunda-platform-8.9`        | Runs SM tests against the 8.9 directory. This is where the `release-candidate-8.9` branch is located |
 | `camunda-platform-8.8`        | Runs SM tests against the 8.8 directory. This is where the `release-candidate-8.8` branch is located |
 | `camunda-platform-8.7`        | Runs SM tests against the 8.7 directory. This is where the `release-candidate-8.7` branch is located |
@@ -584,26 +588,25 @@ This applies to all changes that touch test specs, page objects, fixtures, or ut
 
 The [SaaS/SM/C8Run PR](https://github.com/camunda/c8-cross-component-e2e-tests/actions/workflows/playwright.yml) workflow runs automatically on every pull request. It detects which `tests/` and `pages/` sub-directories have changed and runs the tests for those versions/platforms.
 
-**This works reliably only when a PR touches a single version and a single platform, or only SaaS versions.** Examples that work automatically:
+Every changed version gets its own run, so a PR can span several versions and platforms. Examples:
 
 - Only `tests/8.10/` and/or `pages/8.10/` are changed → 8.10 SaaS tests run.
 - `tests/8.9/` and `tests/8.10/` are changed → 8.9 and 8.10 SaaS tests run, each in its own organization.
-- Only `tests/SM-8.9/` and/or `pages/SM-8.9/` are changed → SM-8.9 tests run.
+- `tests/SM-8.8/` and `tests/SM-8.10/` are changed → one Helm install and test run for each SM version.
+- `tests/c8Run-8.8/` and `tests/c8Run-8.10/` are changed → one c8Run build for each version and Tasklist project.
+- `tests/8.10/` and `tests/SM-8.10/` are changed → the SaaS and the SM runs both start.
 
 If no `tests/` or `pages/` folders are changed (e.g. infrastructure or tooling changes), the test run is skipped automatically — state this explicitly in the PR description.
 
 #### When you must trigger tests manually
 
-Apart from PRs that change only SaaS versions, the automatic PR workflow **does not reliably cover** changes that span multiple versions or multiple platforms. In those cases you must trigger the relevant on-demand workflows manually — or, preferably, split the PR (see [Multi-version PRs](#multi-version-prs) above).
+The automatic PR workflow covers every changed version and platform. The table below says where you still need an on-demand workflow. Test coverage is not a reason to keep a multi-version PR together: still split large changes for review (see [Multi-version PRs](#multi-version-prs) above).
 
 | Scenario | Action required |
 |---|---|
-| Only one version and one platform changed | Wait for the automatic PR workflow |
-| Multiple SaaS versions changed (e.g. `8.9` + `8.8`) | Wait for the automatic PR workflow — it runs each SaaS version in its own organization |
-| Multiple SM versions changed (e.g. `SM-8.9` + `SM-8.8`) | Trigger [SM On-Demand ≥8.8](https://github.com/camunda/c8-cross-component-e2e-tests/actions/workflows/playwright_sm_manual_install_8_8_plus.yml) or [SM On-Demand ≤8.7](https://github.com/camunda/c8-cross-component-e2e-tests/actions/workflows/playwright_sm_manual.yml) separately for each version, **or split the PR** |
-| SaaS + SM versions changed together (e.g. `8.9` + `SM-8.8`) | Trigger both the SaaS and SM on-demand workflows, **or split the PR** |
+| One or more versions changed, on any platforms (e.g. `8.9` + `8.10`, `SM-8.8` + `SM-8.10`, `8.9` + `SM-8.8`) | Wait for the automatic PR workflow |
 | Connector tests | [SaaS Connectors](https://github.com/camunda/c8-cross-component-e2e-tests/actions/workflows/playwright_saas_connectors.yml) or the relevant SM connector workflow |
-| C8 Run tests (`tests/c8Run-8.x/`) | [C8Run On-Demand Linux](https://github.com/camunda/c8-cross-component-e2e-tests/actions/workflows/playwright_c8Run_tests_manual_linux.yml) |
+| C8 Run tests (`tests/c8Run-8.x/`) on macOS or Windows | [C8Run On-Demand Mac](https://github.com/camunda/c8-cross-component-e2e-tests/actions/workflows/playwright_c8Run_tests_manual_mac.yml) or [C8Run On-Demand Windows](https://github.com/camunda/c8-cross-component-e2e-tests/actions/workflows/playwright_c8Run_tests_manual_windows.yml) — the automatic PR workflow runs c8Run on Linux only |
 
 #### Steps
 

package/package.json

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