@camunda/e2e-test-suite 0.0.617 → 0.0.619

package/README.md

@@ -586,12 +586,35 @@ Before marking a PR as ready for review:
 - [ ] Change scope is appropriate — large multi-version changes are split into separate PRs
 - [ ] A relevant test workflow has been run and **passed**
 - [ ] The workflow run URL is pasted in the PR description
-- [ ] Documentation is updated in TestRail and Confluence if a new test case was added
+- [ ] If new tests were added: add the `testrail-test-case` label after the test run passes to auto-enrich TestRail cases (see [TestRail Integration](#testrail-integration)); update Confluence if applicable
 
 ### TestRail Integration
 
-To ensure our test case documentation on TestRail remains up-to-date, if a PR contains updates to any test file or page file, the associated TestRail test case must be linked in the PR description.
+Test case documentation in TestRail is **automatically synced** from spec files. When a PR adds or modifies test cases, the sync workflow uses AI (GitHub Copilot) to generate human-readable step descriptions directly from the Playwright test code.
 
-If you do not have access to TestRail, please contact the Test Automation Team to request access.
+#### How to trigger the sync
+
+**Option A — Label after a passing test run (recommended)**
+
+1. Run the relevant test workflow and confirm it passes.
+2. Add the `testrail-test-case` label to the PR.
+3. The [Sync TestRail Cases](https://github.com/camunda/c8-cross-component-e2e-tests/actions/workflows/sync-testrail-cases.yml) workflow fires automatically, detects the changed spec files, and enriches the matching TestRail cases with AI-generated steps.
+
+> Re-triggering is easy: remove the label and add it again.
+
+**Option B — Manual dispatch**
+
+Go to [Actions → Sync TestRail Cases → Run workflow](https://github.com/camunda/c8-cross-component-e2e-tests/actions/workflows/sync-testrail-cases.yml) and provide the version and spec file path manually. Useful for one-off enrichment without opening a PR.
+
+#### What the sync does
+
+- Finds the matching TestRail case by automation ID (set by the JUnit reporter) or normalised title.
+- Skips cases that already have steps on the correct template.
+- Re-enriches cases that are on the wrong TestRail template (fixes template + steps in one pass).
+- Calls the GitHub Copilot API to produce Action + Expected Result step rows from the raw Playwright code.
+
+#### Access
+
+If you do not have access to TestRail, contact the Test Automation Team to request access.
 
 Thank you for using the C8 Cross-Component End-to-End Test Suite for Camunda C8 full product stack e2e testing. Happy testing! If you have any questions or need assistance, feel free to reach out to the maintainers for support.

package/dist/pages/8.7/ConsoleOrganizationPage.js

@@ -332,7 +332,19 @@ class ConsoleOrganizationPage {
     }
     async clickAuthorizations() {
         await (0, test_1.expect)(this.authorizations).toBeVisible({ timeout: 60000 });
-        await this.authorizations.click();
+        // The Authorizations tab click sometimes doesn't actually switch the
+        // panel — the click registers but Carbon stays on Details and the
+        // downstream row assertions then poll forever against the wrong tab.
+        // Verify aria-selected after the click and retry with force if needed.
+        for (let i = 0; i < 3; i++) {
+            await this.authorizations.click({ force: i > 0 });
+            const selected = await this.authorizations
+                .getAttribute('aria-selected')
+                .catch(() => null);
+            if (selected === 'true')
+                return;
+            await this.page.waitForTimeout(1000);
+        }
     }
     async authorizedResourceAssertion(processId, maxRetries = 20, timeout = 60000) {
         const url = this.page.url();
@@ -354,7 +366,12 @@ class ConsoleOrganizationPage {
             }
         }
     }
-    async authorizedResourcesAssertion(processIds, maxRetries = 30, perCheckTimeout = 30000) {
+    async authorizedResourcesAssertion(processIds, maxRetries = 10, perCheckTimeout = 30000) {
+        // Was 30 × (30s + 30s) ≈ 30 min budget — far too long, and 30 attempts
+        // hides whether the failure is really "still propagating" or "stuck on
+        // the wrong tab forever". 10 × (30s check + 10s sleep) ≈ ~6.5 min total
+        // gives RBA backend plenty of time to propagate while failing fast on
+        // genuine UI-side regressions.
         const url = this.page.url();
         for (let attempt = 0; attempt < maxRetries; attempt++) {
             try {
@@ -368,7 +385,7 @@ class ConsoleOrganizationPage {
             catch (error) {
                 if (attempt < maxRetries - 1) {
                     console.warn(`Attempt ${attempt + 1} failed. Error: ${error}. Retrying...`);
-                    await (0, sleep_1.sleep)(30000);
+                    await (0, sleep_1.sleep)(10000);
                 }
                 else {
                     throw new Error(`Assertion failed after ${maxRetries} attempts. Last error: ${error}`);

package/package.json

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