mukeshs/twenty_crm
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
Files
391392dd87d22226353f985c30d578a275a61a58
twenty_crm/packages/twenty-e2e-testing
History
Dev Iyer d8ea292321 (#11036) task: remove redundant logout button from settings sidebar (#11050) 
- Removed logout item from settings navigation drawer
- Removed logout locator and method from E2E tests
- Removed logout item from NavigationDrawer story

The logout functionality is now exclusively available through the menu
switcher, making the UI more consistent and reducing duplication.

Closes #11036

<img width="851" alt="Screenshot 2025-03-19 at 9 46 33 PM"
src="https://github.com/user-attachments/assets/3d73ec84-a2b7-4c4d-9605-dc83a9a760c1"
/>

---------

Co-authored-by: Félix Malfait <felix@twenty.com>
2025-03-20 10:08:59 +01:00
..
lib
(#11036) task: remove redundant logout button from settings sidebar (#11050)
2025-03-20 10:08:59 +01:00
tests
322 compact command chips dropdown (#10456)
2025-02-25 16:42:38 +01:00
.env.example
Update playwright (#10927)
2025-03-19 11:29:36 +01:00
.gitignore
E2E tests (#6717)
2024-08-27 11:07:10 +02:00
package.json
Update playwright (#10927)
2025-03-19 11:29:36 +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

README.md

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.