@camunda/e2e-test-suite 0.0.1101 → 0.0.1102

package/README.md

@@ -406,7 +406,7 @@ MCP tests can still be run locally on macOS and Windows using the instructions a
 
 ## Automated Nightly Test Runs
 
-The test suite is configured to run automatically every night. The results of these nightly test runs are published on TestRail. If any test fails during these automated runs, the Designated Responsible Individual (DRI) of the project is notified via email for immediate attention and resolution. On a nightly basis, the test suite is configured to run the following tests:
+The test suite is configured to run automatically every night. The results of these nightly test runs are published as a Playwright HTML report artifact. If any test fails during these automated runs, the Designated Responsible Individual (DRI) of the project is notified via email for immediate attention and resolution. On a nightly basis, the test suite is configured to run the following tests:
 
 Failures are classified into categories (Infrastructure, Flaky, Product, Mixed) to aid triage.
 See [docs/ci-failure-categories.md](docs/ci-failure-categories.md) for the full model and criteria.
@@ -520,8 +520,8 @@ issues or instability, an HTML report automatically opens, facilitating in-depth
 
 ### On the CI:
 
-Within the CI environment, test results are accessible through TestRail, located in the C8 Project folder under Test
-Runs. These reports not only include detailed test results but also feature screenshots. In case of a test failure, you
+Within the CI environment, test results are accessible via the Playwright HTML report artifact attached to the
+GitHub Actions run. These reports not only include detailed test results but also feature screenshots. In case of a test failure, you
 will find the stacktrace. Furthermore, the CI environment offers extensive tools for in-depth analysis of test results
 and reports.
 
@@ -536,7 +536,7 @@ use: {
 ```
 
 Don't keep this enabled, or you'll blow up the disk space quickly. Files are recorded in the `test-results/videos`
-folder locally and to TestRail in the CI.
+folder locally and attached to the Playwright HTML report / uploaded as a build artifact in the CI.
 
 ## Contributing
 
@@ -613,35 +613,6 @@ 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
-- [ ] 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
-
-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.
-
-#### 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.
+- [ ] Update Confluence if applicable
 
 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/test-setup.js

@@ -9,12 +9,9 @@ const crypto_1 = require("crypto");
 const axios_1 = __importDefault(require("axios"));
 const constants_1 = require("./utils/constants");
 async function captureScreenshot(page, testInfo) {
-    // Skip on passed/skipped: this ran for every test regardless of outcome,
-    // and since it's uploaded to TestRail via the testrail_attachment
-    // annotation below, a passing-test screenshot has negligible debugging
-    // value but was a dominant driver of excess TestRail attachment storage.
-    // Skip explicitly on passed/skipped rather than gating on
-    // `=== 'failed'`, so a timed-out or interrupted test -- exactly the
+    // Skip on passed/skipped: a passing-test screenshot has negligible
+    // debugging value. Skip explicitly on passed/skipped rather than gating
+    // on `=== 'failed'`, so a timed-out or interrupted test -- exactly the
     // cases where a screenshot is most useful -- still gets one.
     if (testInfo.status === 'passed' || testInfo.status === 'skipped') {
         return;
@@ -43,10 +40,6 @@ async function captureScreenshot(page, testInfo) {
         path: screenshotPath,
         contentType: 'image/png',
     });
-    testInfo.annotations.push({
-        type: 'testrail_attachment',
-        description: screenshotPath,
-    });
 }
 exports.captureScreenshot = captureScreenshot;
 async function captureFailureVideo(page, testInfo) {
@@ -65,10 +58,6 @@ async function captureFailureVideo(page, testInfo) {
             path: videoPath,
             contentType: 'video/webm',
         });
-        testInfo.annotations.push({
-            type: 'testrail_attachment',
-            description: videoPath,
-        });
     }
 }
 exports.captureFailureVideo = captureFailureVideo;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camunda/e2e-test-suite",
-  "version": "0.0.1101",
+  "version": "0.0.1102",
   "description": "End-to-end test helpers for Camunda 8",
   "repository": {
     "type": "git",
@@ -22,7 +22,6 @@
     "access": "public"
   },
   "scripts": {
-    "sync-testrail": "node scripts/sync-testrail-cases.js",
     "test": "playwright test",
     "test:local": "node --env-file=.env ./runTest.js",
     "lint": "tsc && eslint . --ext .ts",

package/playwright.config.ts

@@ -10,7 +10,7 @@ if (!process.env.CAMUNDA_OPTIMIZE_BASE_URL && process.env.BASE_URL) {
 
 const projectName = process.env.PROJECT! || 'Chromium'; // Default to 'default-project' if PROJECT is not set
 
-const testRailOptions = {
+const junitOptions = {
   embedAnnotationsAsProperties: true,
   outputFile: './test-results/junit-report.xml',
 };
@@ -18,7 +18,7 @@ const testRailOptions = {
 // Define reporters without SlackReporter
 const useReportersWithoutSlack: any[] = [
   ['list'],
-  ['junit', testRailOptions],
+  ['junit', junitOptions],
   ['html', {outputFolder: 'html-report'}],
   ['json', {outputFile: `json-report/results.json`}],
 ];