Skip to main content

EndToEndTests-e2e

Purpose and Production Relevance​

EndToEndTests-e2e is a second Playwright E2E suite with a structure similar to e2e. Treat it as a duplicate, migration, or alternate test suite until ownership is clarified.

Production relevance: test suite, but possible duplicate.

Stack and Main Dependencies​

  • Playwright.
  • TypeScript.
  • Node.js.

Important files and folders:

  • EndToEndTests-e2e/tests
  • EndToEndTests-e2e/pages
  • EndToEndTests-e2e/fixtures
  • EndToEndTests-e2e/docs
  • EndToEndTests-e2e/playwright.config.ts
  • EndToEndTests-e2e/.env.example

Business Responsibilities​

Same likely responsibility as e2e: verify Crimoo user workflows in a browser.

Technical Architecture and Source-Code Entry Points​

The structure mirrors e2e:

  • Tests under tests.
  • Page objects under pages.
  • Fixtures under fixtures.
  • Playwright config at the project root.

Key Data Flows and Service Integrations​

Tests exercise Crimoo through the UI and whatever backend/data-plane services the workflow touches.

Environment, Deploy, and Runtime Notes​

Common commands:

cd EndToEndTests-e2e
npm install
npm run test
npm run test:chromium
npm run test:headed
npm run report

Debugging Checklist​

  • Compare failing tests with equivalent coverage in e2e.
  • Confirm which suite is authoritative before deleting or rewriting tests.
  • Keep environment variables consistent with the target app environment.
  • Use Playwright traces and reports to inspect failures.

Tests or Validation Commands​

cd EndToEndTests-e2e
npm run test
npm run report

Mastery Checklist​

  • Explain how this suite differs from e2e.
  • Identify duplicate tests and decide which suite should own future coverage.
  • Run and debug tests locally.