Prompt
Should I compare screenshots in CI or only before releases?
Latest observation
Oct 10, 2026
OpenAI APIWeb search: off
Usually: do both, but for different goals.
In CI
Use screenshot comparison in CI for fast feedback on visual regressions.
Pros
- Catches UI changes immediately
- Prevents small styling bugs from piling up
- Helps reviewers see exactly what changed
- Good for PRs and main-branch protection
Cons
- Can be noisy if screenshots are flaky
- May slow down builds
- Needs stable test environments and careful baseline management
Before releases
Also run screenshot checks before releases as a final quality gate.
Pros
- Verifies the product state you’re about to ship
- Catches last-minute regressions that slipped through
- Useful for release candidate validation
Cons
- Too late to be the only checkpoint
- Problems found here are more expensive to fix
Practical recommendation
- Run a smaller set in CI on every PR or merge.
- Run a broader, stricter set before release.
- If your app changes often, start with:
- critical pages/components in CI
- full visual suite nightly or pre-release
Best practice
If you can only choose one, choose CI.
That gives the best balance of speed, prevention, and developer experience.
If you want, I can also suggest a testing strategy by team size or app type.