Get Started on Cloud
BasicsAI AgentsPipelinesActions & ServicesEnvironmentsIntegrationsTargetsTestsDomainsSandboxesTerraformTunnelsYAMLBuddy GitCLIAPIFAQ

bdy tests

View as Markdown
$bdy tests [options] [command]

Manage unit tests and visual regression (Storybook, URL captures, 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
Manage visual regression testing across Storybook, URL captures, and test runners
Create a visual test session from an explicit URL list, a URLs file, or a sitemap
Manage unit testing (JUnit XML report uploads, suite linking)

Documentation for bdy v1.25.34

Last modified on Nov 3, 2026

Next pageGetting Started

Examples

Upload junit xml report
bdy tests unit upload "reports/**/*.xml" --format junit-xml$
Preview which files would be uploaded without sending
bdy tests unit upload "reports/**/*.xml" --format junit-xml --dryRun$
Interactively link current directory to a unit test suite
bdy tests unit link$
Link non-interactively to a specific suite
bdy tests unit link -w workspace -p project -s suite-identifier$
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$
Capture an explicit list of urls
bdy tests capture --urls "https://example.com,https://example.com/about"$
Capture from a sitemap and follow links
bdy tests capture --sitemap https://example.com/sitemap.xml --follow$
Capture from a urls file and ignore a globbed selector
bdy tests capture --urlsFile ./urls.txt --ignore "header>.banner"$