ca37f16f58
* Set up E2E tests for staging * update * Update * Update .env.staging.example * Fix node modules * Fix * Attempt to swap local-studio-tests to use the new studio-tests directory * Omit storage state if running tests for local self host * Fix test:local command * Deprecate local-studio-test folder * Rename local studio tests GH action to E2E test
1.7 KiB
Studio E2E Tests
In an effort to make the local + hosted studio more stable, we've added tests which test features which are commonly used in local development. Built with Playwright.
How to run tests
Before running the tests, make sure you've done the following:
- Run
npm installin the root folder of this repo dockerororbstackis currently runningsupabaseCLI is already installed- no other supabase local environment is running (infrastructure environment is ok)
You can run the tests by running npm run test in this folder.
When you run the command, it includes:
- Setting up the local environment using the
supabaseCLI - Extracting the environment variables and saving them into a
.env.testfile in the studio app - Running the
studioapp in dev mode (npm run dev) - Running the tests
- Stopping the
studioapp and the local environment
If the environment does't stop for some reason, you'll see supabase start is already running on the next run. In this
case, just run supabase stop between test runs.
How to write tests
Playwright has a nice Codegen tool which you can use to record your actions:
pnpm codegen:setup
# in a separate terminal
pnpm codegen
How to debug/fix tests
If you've run the tests locally and you want to see the results, Playwright has a UI mode which you can use to run and replay specific tests:
pnpm test -- --ui
It will also record any failing tests when running npm run test in this folder.