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
chore: refactor e2e tests to playwright #5080
base: master
Are you sure you want to change the base?
chore: refactor e2e tests to playwright #5080
Conversation
WIP: will refactors tests one by one and rename the e2e-playwright folder to e2e after its done
WIP: will rename the test and clean it up after i received a feedback from maintainers
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ideally, we need to rewrite existing tests on playwright
+ some refactor our tests, because we have a lot of code duplication
@alexander-akait thanks for your comment, for participating in the gsoc-2024, is this PR a valid patch requirements? if not could you introduce an issue which I can start working on? I'm a master student and a junior developer. regarding the proposal, is there anything specific things to be mentioned on or do you have a template from the previous years? also, if there is a discord of slack channel which I can share the draft version of proposal and receive early feedback, I appreciate it. |
/cc @evenstensberg |
I think this should work for a gsoc project. (90h project) |
Yes, I agree. |
WIP: will refactors tests one by one and rename the e2e-playwright folder to e2e after its done
For Bugs and Features; did you add new tests?
Motivation / Use-Case
It will introduce playwright in the project to replace the existing puppeteer end to end framework.
Breaking Changes
Additional Info