-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setup E2E testing #6360
Comments
Hey @lucasbordeau I would like to take this issue, please assign it to me. |
Any chance I can work on this issue? |
@BarryByte I'll assign you since you're first. |
hey @BarryByte just checking, are you still working on it and made some progress? let us know if its available to take, I'm interested to work on this, also just want to mention, making draft PRs are great way to avoid this workflow. |
sorry, currently i am unable to do take this forward. @lucasbordeau Please assign @Nabhag8848 for this issue. Thank you. |
Twenty starts to have a lot of features and different use cases to test.
When doing refactors we usually try to test the app manually to make sure everything is working as expected.
But as it can now take a long time, we would like to have at least manual e2e tests to launch locally while developing or reviewing PR that involve refactors.
We already have integration tests with storybook and a lot of unit tests with jest, we also have visual regression testing with chromatic.
So e2e should focus on the most basics things to detect bugs :
Where e2e would compound efficiently is to offer us a minimal test coverage on a lot of small workflows because tests are easy to write.
We would see later how to integrate this in CI as it is not the main priority right now.
TODO :
The text was updated successfully, but these errors were encountered: