Local development
Use TDD mode to check UI changes against local baselines. Review them in the dashboard or read the saved screenshots from the CLI.
The two local workflows
Keep a server running
npx vizzly tdd start --opennpm test -- --watchUse this while working on the UI.
Run once and get a report
npx vizzly tdd run "npm test"Use this for a quick check or review before committing.
Local files
TDD mode writes local state under .vizzly/, including:
- baselines
- current screenshots
- diffs
- report data
Read the latest saved captures without a running server or cloud login:
npx vizzly tdd screenshots list --jsonnpx vizzly tdd screenshots list --status failed --jsonnpx vizzly tdd screenshots show <comparison-id> --image all --jsonUse an ID from list to pick a browser or viewport variant. show returns
comparison details and image paths. Check each image’s exists flag, then open
the files to see what changed.
If hasNext is true, use the next --page with the same --page-size and filters.
These commands read the latest saved report. If it might be old, rerun the tests.
When to use cloud baselines
If you want to compare local work against a known remote build, start TDD mode with:
npx vizzly tdd start --baseline-build <build-id>Vizzly downloads that build’s baselines, then compares your captures locally.