Frequently Asked Questions
What does Vizzly do?
Vizzly compares screenshots against baselines so UI regressions are easier to catch and review.
Where should I start?
Start with the Quick Start Guide.
If you already have screenshots, vizzly upload is usually the shortest path. If you want Vizzly inside your test flow, use vizzly run or vizzly tdd.
Will this replace my existing tests?
No. Visual testing complements your existing tests. It catches the visual issues your unit and integration tests do not see.
What is a baseline?
A baseline is the reference screenshot Vizzly compares against.
Why did my screenshot show up as new?
Usually because its identity changed. Check the screenshot name, captured image width, browser, and any configured baseline signature properties.
Will an upload failure fail my tests?
With vizzly run, an upload failure leaves your test command’s exit code unchanged. Vizzly reports the missing uploads and marks its own build as failed. If uploads succeed, --wait can still return a non-zero exit code for visual differences. See upload troubleshooting.
What screenshots can I upload?
PNG, JPEG, and WebP images within the cloud screenshot requirements. Those requirements apply whether you capture through an SDK or upload files from disk.
Can API tokens approve builds?
API tokens are for project-scoped automation. Approval and other interactive review actions usually require a user account and normal app permissions.