Files
twenty/packages/twenty-e2e-testing
Félix Malfait 24873d0c1d Remove versions from package.json (#11658)
Now the source of truth for the version is set during the build process.
We set it as an environment variable from the tags.
We could add it back to the package.json during the build process (from
the git tag), but there is not use for it at the moment since it's not
npm packages.
2025-04-19 23:03:06 +02:00
..
2025-04-18 18:39:43 +02:00
2025-04-18 18:39:43 +02:00
2025-03-19 11:29:36 +01:00
2024-08-27 11:07:10 +02: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.