Tests

In this guide, you’ll set up, run, and work with the included end-to-end (E2E) tests for Open SaaS.

The Tests Directory

You’ll find the Playwright test suite under e2e-tests at the root of the project.

yaml


    .
    ├── e2e-tests/
    │   ├── tests/                  # Test files
    │   ├── README.md              # How to run the tests
    │   ├── ci-start-app-and-db.js # Starts app and DB for CI
    │   ├── playwright.config.ts   # Playwright config
    │   ├── package.json
    │   ├── ...

Run tests locally

Open e2e-tests/
Follow the steps in e2e-tests/README.md to install dependencies and run the suite
Use the same README for any local troubleshooting

Use tests in CI with GitHub Actions

The LaunchPike template does not bundle a workflow file in your project but you can find one at Launchpike repo

Copy the .github/ folder (with e2e-tests.yml) into your repo root to run the tests in CI.

⚠️

WASP_VERSION: Update the WASP_VERSION env var in e2e-tests.yml to match the Wasp version used in your project.

Most of the setup is nailed — great job. In the next section we’ll show you how to update your app without breaking flow, so you can focus on launching and monetizing.