You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was initially tasked with creating the full Playwright test suite for Socialify (MIT license). After many iterations, @wei and I discovered that for the web app UI (not the generated image URLs), we are only about to achieve >99% and never 100% matching screenshots.
At the time @wei and I thought this is within the natural margin of error.
However, as I'm building my own OSUSWE App at https://github.com/KemingHe/osuswe-app (GPL 3.0 license) using similar tech stack: NextJS 15, Tailwind+DaisyUI, Playwright+GitHub Actions, I noticed that my screenshot tests (with almost identical setup) are able to achieve 100% UI matches very consistently.
This really raises a big question to the source of Socialify's page UI "volatility", for lack of a better term. And I encourage new contributors to use this opportunity to go over the codebase and learn about our architecture as your fist step to contributing.
Edit: grammar
The text was updated successfully, but these errors were encountered:
Suggested tags: good-first-issue, help-wanted, question, bug
Context
I was initially tasked with creating the full Playwright test suite for Socialify (MIT license). After many iterations, @wei and I discovered that for the web app UI (not the generated image URLs), we are only about to achieve >99% and never 100% matching screenshots.
At the time @wei and I thought this is within the natural margin of error.
However, as I'm building my own OSUSWE App at https://github.com/KemingHe/osuswe-app (GPL 3.0 license) using similar tech stack: NextJS 15, Tailwind+DaisyUI, Playwright+GitHub Actions, I noticed that my screenshot tests (with almost identical setup) are able to achieve 100% UI matches very consistently.
This really raises a big question to the source of Socialify's page UI "volatility", for lack of a better term. And I encourage new contributors to use this opportunity to go over the codebase and learn about our architecture as your fist step to contributing.
Edit: grammar
The text was updated successfully, but these errors were encountered: