TDD mode
Full CLI reference for v0.31.0, published . Cloud features may behave differently today.
TDD mode compares screenshots on your machine. Use tests that capture through
a Vizzly client. Local baselines, screenshots, and reports live under
.vizzly/. Add that directory to .gitignore.
Run tests once
npx vizzly tdd run "npm test" --no-openThis runs the tests and leaves the browser closed. Omit --no-open to open
the report. When differences should fail the run, add --fail-on-diff.
After reviewing a change, update the local baseline with a deliberate run:
npx vizzly tdd run "npm test" --no-open --set-baselineComparison data is saved in .vizzly/report-data.json. When the command prints a static report path, save that report directory as a CI artifact. If a run ends without producing an HTML report, use tdd start --open and rerun the tests against its live dashboard.
Keep the dashboard open
npx vizzly tdd start --opennpx vizzly tdd statusnpx vizzly tdd listnpx vizzly tdd stopRun your tests in another terminal while the server is running. start
prints the dashboard URL. The usual port is 47392; use the URL that start
prints when another port is selected. Pass --port on start to choose a port.
If a running server cannot be reached, check tdd list before starting another one.
Use an approved cloud baseline
npx vizzly tdd run "npm test" --baseline-build build-id --no-openUse --baseline-comparison for a single comparison. These options need
cloud authentication.
Read local results
Read the saved local results with the context command available in this release:
npx vizzly context build current --source local --jsonSee scripting for cloud API requests and JSON output.