bdy tests

## 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$

## 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"$