mirror of
https://github.com/twentyhq/twenty.git
synced 2024-12-23 20:13:21 +03:00
7943141d03
## Summary Add support for multi-workspace feature and adjust configurations and states accordingly. - Introduced new state isMultiWorkspaceEnabledState. - Updated ClientConfigProviderEffect component to handle multi-workspace. - Modified GraphQL schema and queries to include multi-workspace related configurations. - Adjusted server environment variables and their respective documentation to support multi-workspace toggle. - Updated server-side logic to handle new multi-workspace configurations and conditions. |
||
---|---|---|
.. | ||
config | ||
drivers | ||
lib | ||
tests | ||
.env.example | ||
.gitignore | ||
package.json | ||
playwright.config.ts | ||
README.md |
Twenty e2e Testing
Prerequisite
Installing the browsers:
yarn playwright install
Run end-to-end tests
yarn run test:e2e
Start the interactive UI mode
yarn run test:e2e:ui
Run test only on Desktop Chrome
yarn run test:e2e:chrome
Run test in specific file
yarn run test:e2e <filename>
Runs the tests in debug mode.
yarn run test:e2e:debug
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.