Testing

Playwright: Automated Browser Testing

How e2e tests work (Playwright)

For guidance on writing stable, non‑flaky Playwright tests (including patterns for parallel runs, retries, timeouts, fixtures, network stubbing and selectors), follow Playwright's official best practices:

• https://playwright.dev/docs/best-practices

If you need an internal quick reference, keep tests small and deterministic, use page.locator() + expect matchers, prefer API setup over UI setup, and wait for network or specific selectors rather than using fixed timeouts.

Unit-style tests

Frontend logic is tested with Playwright as well - there is no separate mocha/jsdom runner anymore.

• Pure client functions (helpers without DOM or webpack-only imports) can be exercised directly in a spec: import tests/e2e/helpers/client-module-shim first, then import the client module and assert synchronously. Example: specs/i18n-escape.spec.ts.
• Component behaviour is asserted through the rendered UI in a normal e2e spec, see specs/tabbed-page.spec.ts for a converted component test.

Quick Start

Prerequisites: Docker and Docker Compose installed

Run all tests:

./scripts/test-e2e

Run specific test:

./scripts/test-e2e specs/LoginTest.spec.ts

Usage

Command	Purpose
./scripts/test e2e	Run all E2E tests (includes DB setup)
./scripts/test-e2e	Run E2E tests only (requires test env running)
./scripts/test-e2e <file>	Run specific test file
./scripts/test-e2e --workers=2	Run with custom worker count
./scripts/test-e2e debug	Open interactive shell for manual testing

More options: https://playwright.dev/docs/running-tests

Interactive Mode

For development and debugging:

./scripts/test-e2e debug

Inside the container:

yarn test                           # Run all tests
yarn test specs/LoginTest.spec.ts  # Run specific test
yarn test --workers=2               # Adjust parallelization
yarn test:ui                        # Run tests with browser UI. Open browser on host at http://localhost:23008
exit                                # Leave container

Press CTRL-C to stop tests gracefully and view the HTML report.

Test Reports

After tests you can open the report with:

yarn show-report

Artifacts:

• Results: tests/_output/test-results/
• HTML report: tests/_output/html-report/

Setup

Docker: Tests run in foodsharing_test_e2e container with Chromium, Firefox, and WebKit pre-installed.

Linting: Pre-commit hooks via Husky are installed automatically with yarn install in tests/e2e/.

To bypass: git commit --no-verify

To stop the Test containers run ./scripts/stop test.