179d3ae2a4
- Refactor the handles: the source handles are now part of the edges as markerStart - **As the source handles are now part of the edges, we can delete the `markLeafNodes` logic; this can be done in another PR**. See https://github.com/twentyhq/core-team-issues/issues/386 - Create a custom edge component for the default edge - Create a custom edge component for the success edge; this includes a label **The edges can be tested in Storybook. I wrote two stories for the edges.** | Default | Success | |--------|--------| |  |  |
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.