mirror of
https://github.com/twentyhq/twenty.git
synced 2024-11-22 11:43:34 +03:00
736635a94b
We will remove the `twenty-postgres` image that was used for local development and only use `twenty-postgres-pilo` (which we use in prod), bringing the development environment closer to prod and avoiding having to maintain 2 images. Instead of provisioning the super user after the db initialization, we directly rely on the superuser provided by Spilo for simplicity. We also introduce a change that tries to create the right database (`default` or `test`) based on the context. How to test: ``` docker build -t twentycrm/twenty-postgres-spilo:latest -f ./packages/twenty-docker/twenty-postgres-spilo/Dockerfile . docker images --no-trunc | grep twenty-postgres-spilo postgres-on-docker: docker run \ --name twenty_pg \ -e PGUSER_SUPERUSER=twenty \ -e PGPASSWORD_SUPERUSER=twenty \ -e ALLOW_NOSSL=true \ -v twenty_db_data:/home/postgres/pgdata \ -p 5432:5432 \ REPLACE_WITH_IMAGE_ID ``` |
||
|---|---|---|
| .. | ||
| config | ||
| drivers | ||
| lib | ||
| tests | ||
| .env.example | ||
| .gitignore | ||
| package.json | ||
| playwright.config.ts | ||
| README.md | ||
Twenty e2e Testing
Prerequisite
Installing the browsers:
yarn playwright install
Run end-to-end tests
yarn run test:e2e
Start the interactive UI mode
yarn run test:e2e:ui
Run test only on Desktop Chrome
yarn run test:e2e:chrome
Run test in specific file
yarn run test:e2e <filename>
Runs the tests in debug mode.
yarn run test:e2e:debug
Q&A
Why there's path.resolve() everywhere?
That's thanks to differences in root directory when running tests using commands and using IDE. When running tests with commands,
the root directory is twenty/packages/twenty-e2e-testing, for IDE it depends on how someone sets the configuration. This way, it
ensures that no matter which IDE or OS Shell is used, the result will be the same.