Run end-to-end (E2E) tests¶

Gitrust's E2E tests use Playwright to drive a Chromium browser against an instance of the application configured with a dedicated database and repository directory.

Prerequisites¶

• Node.js (already present for Tailwind/DaisyUI)
• PostgreSQL accessible locally (Docker via database/docker-compose.yml)
• psql, createdb, dropdb available in the PATH
• Chromium installed via Playwright (npx playwright install chromium)

Orders¶

# Créer (ou remettre à zéro) la base de données de test
npm run test:e2e:setup

# Lancer tous les tests E2E
npm run test:e2e

# Mode debug interactif (inspecteur Playwright, pas-à-pas)
npm run test:e2e:debug

# Mode UI (interface graphique Playwright)
npm run test:e2e:ui

# Consulter le rapport HTML après exécution
npm run test:e2e:report

Architecture¶

.env.test                         # Variables d'environnement de test
playwright.config.ts              # Configuration Playwright

scripts/
  e2e-setup-db.sh                 # Crée la DB gitrust_test + nettoie depot_test
  e2e-server.sh                   # Démarre l'app avec .env.test

tests/e2e/
  fixtures.ts                     # Fixtures partagées (loginAs, credentials)
  global-setup.ts                 # Seed : crée les utilisateurs via /register
  global-teardown.ts              # Nettoyage post-tests
  auth.spec.ts                    # Tests d'authentification
  repository.spec.ts              # Tests de gestion des dépôts
  admin.spec.ts                   # Tests du panneau d'administration
  navigation.spec.ts              # Tests de navigation et UI

Isolation of the test environment¶

Functioning¶

1. npm run test:e2e:setup deletes then recreates the gitrust_test database and empties depot_test/.
2. Playwright automatically starts the application via scripts/e2e-server.sh, which loads the variables from .env.test before executing cargo run.
3. The global-setup creates the test users (alice, bob, charlie) using the /register form — 100% E2E approach, no direct insertion into the database.
4. The tests run sequentially (a single worker) to avoid conflicts on the shared DB.
5. The global-teardown is executed at the end of the session.

Fixtures¶

The fixtures.ts file provides a loginAs fixture that is reusable in all tests:

import { test, expect } from './fixtures';

test('mon test', async ({ page, loginAs }) => {
  await loginAs('alice');
  // alice est connectée, on peut naviguer
});

Available users: admin, alice, bob, charlie.

List of tests¶

auth.spec.ts — Authentication¶

repository.spec.ts — Repository management¶

admin.spec.ts — Administration¶

navigation.spec.ts — Navigation and UI¶

Add a new test¶

1. Create a tests/e2e/mon-module.spec.ts file
2. Import fixtures: import { test, expect } from './fixtures';
3. Use loginAs for tests requiring authentication
4. Run with npm run test:e2e or target the file: npx playwright test my-module