Skip to content

ci: add Playwright e2e test job to CI workflow #102

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
field123 wants to merge 3 commits into
base: master
Choose a base branch
from
Open

ci: add Playwright e2e test job to CI workflow #102

field123 wants to merge 3 commits into from

Conversation

@field123
Copy link
Collaborator

@field123 field123 commented Jan 26, 2026 •
edited
Loading

Changes

  • New test-e2e job that:

    • Sets up PostgreSQL 15 with test users and extensions
    • Seeds the database with test data (yarn seed)
    • Builds the frontend and starts all application servers (backend:3004, host:3005, frontend:3003)
    • Runs all 68+ Playwright tests with 8 parallel workers
    • Uploads artifacts (playwright-report always, test-results on failure)

  • Updated all-tests job to include e2e results in the summary table

Trigger Conditions

Same pattern as test-wab:

  • Manual trigger: Via GitHub Actions UI
  • Push to master: Runs automatically
  • PRs: Only when labeled with run-e2e-tests

@field123
ci: add Playwright e2e test job to CI workflow
2231e5d 
Add a new test-e2e job that runs all Playwright e2e tests:
- Triggered by 'run-e2e-tests' label on PRs (same pattern as test-wab)
- Sets up PostgreSQL with test users and seeds database
- Builds frontend and starts all application servers
- Runs Playwright tests with 8 workers and 2 retries
- Uploads test artifacts (reports, screenshots, videos on failure)
- Updates all-tests job to include e2e results in summary
@field123
ci: fix e2e test database setup
05e0e54 
- Add -U postgres flag to psql commands (PGUSER env var not picked up)
- Add -d wab flag for extensions (must be in wab database, not postgres)
- Add TypeORM migration step before seeding
@field123
ci: use development build to bypass analytics env vars
e116781 
Production builds require AMPLITUDE_API_KEY and other analytics env vars.
Set NODE_ENV=development for the build step to bypass this requirement.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

run-e2e-tests

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@field123