twentyhq/twenty
1
1
Fork 0
mirror of https://github.com/twentyhq/twenty.git synced 2024-12-23 03:51:36 +03:00
Code Issues Packages Projects Releases Wiki Activity
0a0be421d7
twenty/packages/twenty-e2e-testing
History
BOHEUS c754585e47
Basic test verifying if demo account is working properly (#8442)
2024-12-17 13:56:00 +01:00
..
config E2E tests (#6717) 2024-08-27 11:07:10 +02:00
drivers feat(*): allow to select auth providers + add multiworkspace with subdomain management (#8656) 2024-12-03 19:06:28 +01:00
lib Playwright tests - stage 1 - login with email and password test (#8988) 2024-12-12 11:05:25 +01:00
tests Basic test verifying if demo account is working properly (#8442) 2024-12-17 13:56:00 +01:00
.env.example Playwright tests - stage 1 - login with email and password test (#8988) 2024-12-12 11:05:25 +01:00
.gitignore E2E tests (#6717) 2024-08-27 11:07:10 +02:00
package.json feat(e2e): twenty-e2e-testing with playwright (#6539) 2024-08-14 17:23:32 +02:00
playwright.config.ts Basic test verifying if demo account is working properly (#8442) 2024-12-17 13:56:00 +01:00
README.md E2E tests (#6717) 2024-08-27 11:07:10 +02:00

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.