-
Notifications
You must be signed in to change notification settings - Fork 196
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
frontend: edit docs for playwright #1930
Conversation
9b523e5
to
cd52353
Compare
Something that could be useful is a development guide, like how to create, change and validate tests and also how to run tests against a local frontend build. Also we should probably mention the |
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.
Left a comment. Otherwise, it feels like Olek's idea of mentioning --ui is a good one.
@skoeva Can you confirm/test these steps? |
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.
other than these changes, LGTM
Signed-off-by: Vincent T <vtaylor@microsoft.com>
rebased and added a section for the UI mode |
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.
🎉🎈 Thanks.
Requested changes were done, and there was a "LGTM otherwise".
Update Documentation for Local Playwright End-to-End Tests
Description
This PR updates the existing documentation to include more detailed instructions on setting up and running local Playwright end-to-end tests. The enhancements aim to provide developers with clear guidelines on how to effectively utilize Playwright for testing their local developments, ensuring that they can quickly and efficiently verify changes before deployment.
Changes
Verification