-
Notifications
You must be signed in to change notification settings - Fork 5
chore(playwright): add initial playwright support #273
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
All alerts resolved. Learn more about Socket for GitHub. This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. Ignoring alerts on: |
@SocketSecurity ignore npm/[email protected] |
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.
Ran this inside a devcontainer locally and it all worked! Nice.
Got partially through #252 and realized manually verifying css parity was quite annoying.
Here I've integrated playwright and written a test to do screenshot diffing on applicable routes which should be a good sanity check.
I've tried to tighten down the threshold but fonts & antialiasing mean there may need to be some tweaks.