twenty/packages/twenty-e2e-testing
Antoine Moreaux 00d12e854a
BREAKING - feat(auth): refactor tokens logic & enhance email verification flow (#13487)
- Replaced `getAuthTokensFromLoginToken` with
`getAccessTokensFromLoginToken` for clarity.
- Introduced `getWorkspaceAgnosticTokenFromEmailVerificationToken`.
- Extended mutation inputs to include `locale` and
`verifyEmailNextPath`.
- Added email verification check and sending to various handlers.
- Updated GraphQL types and hooks to reflect these changes.


Fix #13412

---------

Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Co-authored-by: Félix Malfait <felix.malfait@gmail.com>
Co-authored-by: Félix Malfait <felix@twenty.com>
2025-07-31 12:00:59 +02:00
..
lib BREAKING - feat(auth): refactor tokens logic & enhance email verification flow (#13487) 2025-07-31 12:00:59 +02:00
tests Fix most e2e tests (#13282) 2025-07-18 21:40:46 +02:00
.env.example Verify seed users and change AppleCar password (#11825) 2025-04-30 16:59:13 +00:00
.gitignore E2E tests (#6717) 2024-08-27 11:07:10 +02:00
package.json Remove versions from package.json (#11658) 2025-04-19 23:03:06 +02: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.