twenty/packages/twenty-e2e-testing
Félix Malfait 7a0f2f8c0a
Add logged out translations (#9983)
Add translation for logged in / sub pages
2025-02-03 22:00:54 +01:00
..
lib Add logged out translations (#9983) 2025-02-03 22:00:54 +01:00
tests Add logged out translations (#9983) 2025-02-03 22:00:54 +01:00
.env.example Workflow e2e tests – 1st batch (#9713) 2025-01-20 10:59:01 +01:00
.gitignore E2E tests (#6717) 2024-08-27 11:07:10 +02:00
package.json preparing version 0.42-caanry (#9938) 2025-02-03 10:53:05 +01:00
playwright.config.ts Workflow e2e tests – 1st batch (#9713) 2025-01-20 10:59:01 +01:00
project.json Workflow e2e tests – 1st batch (#9713) 2025-01-20 10:59:01 +01:00
README.md Add NX commands to twenty-e2e-testing package (#9222) 2024-12-31 15:49:52 +01:00

Twenty end-to-end (E2E) Testing

Prerequisite

Installing the browsers:

npx nx setup twenty-e2e-testing

Run end-to-end tests

npx nx test twenty-e2e-testing

Start the interactive UI mode

npx nx test:ui twenty-e2e-testing

Run test in specific file

npx nx test twenty-e2e-testing <filename>

Example (location of the test must be specified from the root of twenty-e2e-testing package):

npx nx test twenty-e2e-testing tests/login.spec.ts

Runs the tests in debug mode.

npx nx test:debug twenty-e2e-testing

Show report after tests

npx nx test:report twenty-e2e-testing

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.