-
Notifications
You must be signed in to change notification settings - Fork 70
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
feat(playwright): setup and config #11836
Conversation
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.
Fremragende arbeid! Har noen små forslag, men ser ikke noe jeg mener er kritisk. Overlater denne til resten av teamet nå siden jeg ikke er tilbake på jobb før neste uke.
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.
This looks very good, impressive work👏🏻 I have a question and one suggestion 😄
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.
LGTM 😄
Description
Playwright Configuration for End-to-End (e2e) Tests in Studio
Have configured Playwright to write end-to-end (e2e) tests in Studio. We have a team meeting after the New Year that will focus on defining a test strategy. Therefore, new tests should not be created until we have completed the meeting and documented our desired testing approach.
Changes in this Pull Request (PR)
simple-schema-app
that logs in and creates an app.Note
I have created a own issue to ensure to run this tests within the pipeline on PR and merge to master. We do also need to ensure that the test reports is presented within the Github interface. issue 11991
Related Issue(s)
Verification