-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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(cleanup): remove legacy visual regression tests #19527
Conversation
4df2973
to
9bf54ca
Compare
c17b574
to
017da76
Compare
9bf54ca
to
254db22
Compare
017da76
to
aaf6e40
Compare
This PR hasn't seen activity in a week! Should it be merged, closed, or further worked on? If you want to keep it open, post a comment or remove 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.
While I think there's a bit of value to these tests, I agree they're very crufty, so alright – let's get rid of them
# Conflicts: # playwright/e2e-vrt/lemon-ui/LemonButton.spec.ts-snapshots/Lemon-Button-displays-disabled-reason-correctly-1-chromium-linux.png
Problem
We have two separate ways to run visual regression tests: (a) Page objects that we customize manually (b) Screenshots of storybook while using storybook features to achieve the desired UI state. We've pretty much chosen approach 2 so far an. Let's revisit page objects and Playwright once we look into e2e tests again.
Changes
This PR removes legacy tests, since we are hardly using them any more & this simplifies our setup.
How did you test this code?
CI run