-
Notifications
You must be signed in to change notification settings - Fork 339
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
Only run visual regression tests if there are code changes that might cause a visual change #2864
Comments
We could also only do the split JS/non-JS variants for components that have JavaScript. |
Some suggestions from me:
|
We're also running the Tests workflow twice for every push to a pull request .github/workflows/tests.yml on: [push, pull_request] |
I think this closed by #2878. |
Going to reopen this one as we've still running Percy for code changes that don't affect component UI |
We're now running We could use this information (e.g. no diff, nothing has changed) to prevent Percy from running |
Some time later, but here's an example of how to use - name: Run backstop
run: npm run test:visual
+ if: ${{ steps.changes.outputs.changes == 'true' }} |
What
Only run Percy's visual regression tests if there are code changes that might cause a visual change.
As a (non-exhaustive) example, do not run visual regression tests if the only files changed in a PR are tests, docs, internal tooling, or in the dist and package folder.
Why
We have a limited number of screenshots available to us in any given billing period. Only running the visual regression tests when they are useful helps us to burning through our included screenshots too quickly, allowing us to remain on a cheaper plan.
Who needs to work on this
Developers
Who needs to review this
Developers
Done when
The text was updated successfully, but these errors were encountered: