Test Reporting with ReportPortal

E2E test results from Playwright are sent to ReportPortal in real-time during pipeline execution.

How It Works

1. Playwright E2E tests run in the verify stage (after deployment to DEV)
2. Results stream to ReportPortal as tests execute
3. Launch created in ReportPortal with all test results
4. Dashboard updated with pass/fail trends

Pipeline Job

The E2E test job runs Playwright and reports to ReportPortal:

e2e:
  stage: verify
  image: mcr.microsoft.com/playwright:latest
  script:
    - cd platform/ui
    - npm ci
    - npm run e2e
  tags:
    - medium

The ReportPortal integration is configured in playwright.config.ts using the @reportportal/agent-js-playwright reporter.

Running E2E Tests Locally

cd platform/ui

# Headless (same as CI)
npm run e2e

# With browser visible (debugging)
npm run e2e:headed

# Interactive Playwright UI
npm run e2e:ui

# Record tests
npm run e2e:codegen

Viewing Results in ReportPortal

1. Open ReportPortal
2. Select the orchestrator-ui project
3. Click Launches to see test runs
4. Click a launch to drill into individual test results
5. Failed tests show error messages and screenshots

Test Structure

E2E tests follow the Page Object Model pattern:

platform/ui/e2e/
├── fixtures/          # Test fixtures and auth setup
├── pages/             # Page objects (LoginPage, DashboardPage, etc.)
├── tests/             # Test files
└── playwright.config.ts

Writing New E2E Tests

1. Create a page object in e2e/pages/ if the page doesn't exist
2. Write test in e2e/tests/
3. Use fixtures for authentication and common setup
4. Run locally first, then push to trigger CI