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
While working, I found a common case when I cannot generate the same screenshots as on CI because I use macOS and CI as usual Linux. I created a simple workaround: I added docker-compose into the project with the same setup as on CI and ran it when I needed to update screenshots. But still, some screenshots are not the same on CI and locally because it's hard to stabilize them.
In order to debug the issue, I need to download the changed files from CI, unpack them, and locally compare them. However, it requires a lot of steps and time to find appropriate problem screenshots if there are many of them and a deep tree structure.
Current Workaround
So, I created a simple report page that shows all changes as one HTML file and created GitHub actions to post links to the zip (still zip because of GitHub actions limitations) per PR to download the report. This looks like
Other options
Upload to static site hosting
My idea was to use https://surge.sh to upload them. But in order to set up such infrastructure, you need to do several steps, which would fright others to use.
Think about the option to compare between branches
Please help me to find the best approach, which could be minimal or at least be like an extension to our current gem, and help to reduce steps on PR review.
What would you suggest to use?
Is it possible to avoid cloud solutions like Percy? Do not reinvent the wheel.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Context
While working, I found a common case when I cannot generate the same screenshots as on CI because I use macOS and CI as usual Linux. I created a simple workaround: I added docker-compose into the project with the same setup as on CI and ran it when I needed to update screenshots. But still, some screenshots are not the same on CI and locally because it's hard to stabilize them.
In order to debug the issue, I need to download the changed files from CI, unpack them, and locally compare them. However, it requires a lot of steps and time to find appropriate problem screenshots if there are many of them and a deep tree structure.
Current Workaround
So, I created a simple report page that shows all changes as one HTML file and created GitHub actions to post links to the zip (still zip because of GitHub actions limitations) per PR to download the report. This looks like

Other options
Upload to static site hosting
My idea was to use
https://surge.sh
to upload them. But in order to set up such infrastructure, you need to do several steps, which would fright others to use.Think about the option to compare between branches
As Pronto Gem does, instead of comparing with the last commit, compare with another branch like
main.
There are some similarities. Ex. github actions: https://github.com/reg-viz/reg-actions?tab=readme-ov-file#minimal-setup But it's pretty complicated because we need to store metadata like exact skip areas.CTA
Please help me to find the best approach, which could be minimal or at least be like an extension to our current gem, and help to reduce steps on PR review.
Beta Was this translation helpful? Give feedback.
All reactions