diff --git a/docs/e2e-tests/CI-medic-guide.md b/docs/e2e-tests/CI-medic-guide.md index e9c0dd0016..cb6ae5c9db 100644 --- a/docs/e2e-tests/CI-medic-guide.md +++ b/docs/e2e-tests/CI-medic-guide.md @@ -88,7 +88,7 @@ When your rotation begins: 1. **Read the [Overview](#overview)** above to understand the role and where alerts come in. 2. **Familiarize yourself with the [Useful Links and Tools](#useful-links-and-tools)** section -- open the Prow dashboards, join the Slack channels, and make sure you have access. -3. **Review the [Internal Resources doc](https://docs.google.com/document/d/1yiMU-u2v8_rC-TBawcaJwV5jAvWcbTjhspuTe3KNcCo/edit?usp=sharing)** -- it covers Vault secrets, ReportPortal dashboards, DevLake analytics, and how to unredact artifacts. These are internal tools you'll need during triage. +3. **Review the [Internal Resources doc](https://docs.google.com/document/d/1yiMU-u2v8_rC-TBawcaJwV5jAvWcbTjhspuTe3KNcCo/edit?usp=sharing)** -- it covers Vault secrets, DevLake analytics, and how to unredact artifacts. These are internal tools you'll need during triage. 4. **Try the [AI Test Triager](#ai-test-triager-nightly-test-alerts)** on a recent **RHDH Core** failure in `#rhdh-e2e-alerts` to see how it works. It will handle most of the initial Core analysis for you. 5. **Open a recent overlay alert** and follow its **E2E AI Triage Summary** link. Skim the classification table so you know what fullsend produces before your first real overlay failure. See [Overlay Nightly Failures (Fullsend)](#overlay-nightly-failures-fullsend). @@ -765,7 +765,7 @@ Use [`.ci/pipelines/trigger-nightly-job.sh`](../../.ci/pipelines/trigger-nightly ### Related Documentation -- [Internal Resources (Google Doc)](https://docs.google.com/document/d/1yiMU-u2v8_rC-TBawcaJwV5jAvWcbTjhspuTe3KNcCo/edit?usp=sharing) -- Vault secrets, ReportPortal, DevLake, unredacting artifacts (Red Hat internal) +- [Internal Resources (Google Doc)](https://docs.google.com/document/d/1yiMU-u2v8_rC-TBawcaJwV5jAvWcbTjhspuTe3KNcCo/edit?usp=sharing) -- Vault secrets, DevLake, unredacting artifacts (Red Hat internal) - [`.ci/pipelines/README.md`](../../.ci/pipelines/README.md) -- cluster pools, access requirements, development guidelines - [`.ci/pipelines/lib/README.md`](../../.ci/pipelines/lib/README.md) -- full list of pipeline library modules and function signatures - [`CI.md`](CI.md) -- CI testing processes, job definitions, openshift/release repo links diff --git a/docs/e2e-tests/CI.md b/docs/e2e-tests/CI.md index 446cf4bf1c..4389854627 100644 --- a/docs/e2e-tests/CI.md +++ b/docs/e2e-tests/CI.md @@ -68,7 +68,6 @@ If the initial automatically triggered tests fail, OpenShift-CI will add a comme 4. **Artifact Collection:** - Collects test artifacts (logs, screenshots, recordings). - Stores artifacts in the designated `ARTIFACT_DIR` for a retention period of **6 months**. - - The reports are also sent to _ReportPortal_ 5. **Reporting:** - Reports status back to the PR checks. - Generates and uploads HTML reports. diff --git a/docs/e2e-tests/enhanced-ci-reporting.md b/docs/e2e-tests/enhanced-ci-reporting.md index b66ba4e6cb..afcf62105c 100644 --- a/docs/e2e-tests/enhanced-ci-reporting.md +++ b/docs/e2e-tests/enhanced-ci-reporting.md @@ -77,7 +77,6 @@ All status information is written to files in the `SHARED_DIR` directory, which - `SHARED_DIR/STATUS_FAILED_TO_DEPLOY.txt` - Deploy failure flags (one per line) - `SHARED_DIR/STATUS_TEST_FAILED.txt` - Test failure flags (one per line) - `SHARED_DIR/STATUS_NUMBER_OF_TEST_FAILED.txt` - Failure counts (one per line) -- `SHARED_DIR/STATUS_URL_REPORTPORTAL.txt` - ReportPortal URLs - `SHARED_DIR/OVERALL_RESULT.txt` - Single value These files are also copied to `ARTIFACT_DIR/reporting/` for artifact collection. @@ -126,7 +125,7 @@ The `redhat-developer-rhdh-send-alert` step is defined in the [OpenShift release - Formats the collected status information into structured Slack messages - Sends notifications to the `#rhdh-e2e-alerts` channel - Handles multiple deployments and their individual test results -- Provides links to job logs, artifacts, and ReportPortal results +- Provides links to job logs, Playwright reports, and artifacts The step is configured in job definitions to run after test execution completes, ensuring all status information is captured and reported. @@ -141,7 +140,7 @@ For nightly runs, the system automatically sends notifications to the `#rhdh-e2e - **Deployment Label**: e.g., `showcase`, `showcase-rbac`, `showcase-runtime` - **Deployment Status**: "deployed" status - **Test Results**: "tests passed" or failure count (e.g., "2 tests failed") - - **Tools**: Playwright, ReportPortal, and artifacts links + - **Tools**: Playwright and artifacts links ## File Locations