Files
shumai/apps/web/e2e

Web App E2E Tests

Fullstack end-to-end tests for the Shumai web app. They run against a real backend (pgvector container + local S3 storage) served on http://localhost:5200 and are executed with Playwright via bun run test:e2e.

Structure

apps/web/e2e/
├── fixtures.ts          # prisma / owner / project / file fixtures
├── serve.ts             # starts the test DB container + web app
├── global-teardown.ts   # stops the container and cleans up storage
├── helpers/
│   ├── auth.ts          # signup / auth-state injection helpers
│   ├── project.ts       # project creation helpers
│   ├── files.ts         # share link API helpers
│   ├── team.ts          # team member seeding helpers
│   └── ui.ts            # common UI flows (signup, login, members dialog)
└── tests/<domain>/      # domain-scoped specs (auth, team, project)

Fixtures

  • prisma — auto fixture that truncates all tables before each test. Also the direct way to read/write DB state for assertions and seeding.

  • owner — an authenticated team owner (seeded through the API), with the session cookie and auth state injected into the browser context, opened on the team page.

  • project — owner plus a project created through the API (projectId, projectName).

  • file — project plus a seeded processed file asset in the project root (fileId, fileName). The media kind is configurable per test via fileOptions (default binary):

    // default binary file (no extension, no proxy)
    test('...', async ({ file }) => {})
    
    // type-scoped file for future viewer/transcode tests
    test('...', { fileOptions: { mediaType: 'image' } }, async ({ file }) => {})
    
    mediaType filename notes
    binary (default) test-file-<ts> never transcoded, no proxy
    text test-file-<ts>.txt gets a PDF proxy in real usage
    image test-file-<ts>.png
    video test-file-<ts>.mp4
    pdf test-file-<ts>.pdf

Test Cases

auth

Test File
Sign up as the first user and become the team owner tests/auth/signup.spec.ts
Log in with existing credentials tests/auth/login.spec.ts

team

Test File
Owner invites a member via invite link and the invitee joins tests/team/invite-member.spec.ts
Owner removes a member via the members dialog; the membership is deleted from the DB tests/team/remove-member.spec.ts

project

Test File
Owner creates a project with a cover image tests/project/create-project.spec.ts
Owner uploads a file via the "Upload File" context menu action tests/project/upload-file.spec.ts
Owner deletes a file, finds it in recently deleted, and restores it tests/project/delete-restore.spec.ts
Owner creates a share link from a file context menu and lands on the share page tests/project/create-share-link.spec.ts
Owner protects a share with a password; guests must enter it to view tests/project/share-password.spec.ts
Owner creates a collection from the sidebar; the collection shows project files tests/project/create-collection.spec.ts

Conventions

  • Seed data via fixtures/API/DB; use the UI only for the flow under test.
  • Each test truncates all tables via the auto prisma fixture, so fixtures must create their data per-test.
  • App projects run with workers: 1 because all tests share a single database.
  • Every new test case MUST be documented in this README.