bdy tests visual

$bdy tests visual [options] [command]

Manage visual regression testing across Storybook, URL captures, and test runners

OPTIONS

--context <name>

Connection and scope context: default, git, link or a saved name. Overrides the globally active context for this invocation.

--examples

Show only examples; with this flag --format accepts text, json or jsonl

--verbose

Show REST API requests, responses, timing and retries on stderr

-h, --help

display help for command

AVAILABLE COMMANDS

link

Link current directory to a visual test suite Required scopes: VISUAL_TEST_WRITE

Manage visual test sessions

Install the resource-discovery browser used by `bdy tests visual session create`

Upload a built Storybook to create a visual test session

Documentation for bdy v1.25.34

Last modified on Nov 3, 2026

Examples

Install the resource-discovery browser (needed by `session create` unless --skipDiscovery)

bdy tests visual setup$

Upload a built Storybook to the linked visual test suite

bdy tests visual upload ./storybook-static$

Interactively link current directory to a visual test suite

bdy tests visual link$

Link non-interactively to a specific suite

bdy tests visual link -w workspace -p project -s suite-identifier$

Run your test command with the visual-test plugin server attached

bdy tests visual session create "npm test"$

Skip resource discovery (debugging or asset-free pages)

bdy tests visual session create "npm test" --skipDiscovery$

Send snapshots progressively (quicker review during long runs)

bdy tests visual session create "npm test" --oneByOne$

One runner in a parallel session (every runner must share the same $SNAPSHOTS_BUILD_ID)

bdy tests visual session create "npm test" --parallel$

Close the session after all parallel runners finished (build id read from $SNAPSHOTS_BUILD_ID)

bdy tests visual session close$