WebTest AI v2 beta: coming soon

This is preview documentation for the upcoming release. Publication is pending live Jev validation. The demo uses a live navigator with mocked Jev element selection.

Previous engine and compatibility tools

This page is retained for existing users. It is not the v2 goal-runtime guide. Start with Runtime Configuration or review engine differences before using these features.

webtest-ai discover

Runs a bounded model-backed workflow that proposes candidate browser test flows.

webtest-ai discover --url https://app.example --dry-run
webtest-ai discover --url https://app.example --output artifacts/discovery/app.json
webtest-ai discover --target brand-a-en --target brand-b-fr --dry-run
webtest-ai discover --targets brand-a-en,brand-b-fr --dry-run
webtest-ai discover --target all --explore --max-pages 5 --inventory-output artifacts/discovery/ui-inventory.proposed.json --spec-output artifacts/discovery/discovered.md
webtest-ai discover --target all --explore --auth-profile ci-user --refresh-auth --dry-run

Discovery only calls a model when an active model profile is configured. Exact-step run execution can work without a navigator model; Goal/Success execution requires one. Neither delegates the final browser verdict to the model.

When --target is used, WebTest AI expands configured target baseUrl values into seed URLs and passes target metadata such as brand, locale, and intentAliases to the discovery prompt. If UI inventory memory is enabled and present, discovery also includes the reviewed inventory so proposed flows can build on known intent-to-control mappings without executing browser actions.

When --explore is set, WebTest AI opens the seed URLs with the active driver, crawls same-origin links within the configured page/depth budget, and passes bounded page evidence to the discovery prompt. Evidence includes URL patterns, page fingerprints, accessibility candidates, DOM action candidates, and same-origin links. The model can still only return proposals: candidate flows and optional reviewed UI inventory updates.

Browser-backed exploration can prepare configured auth before opening seed URLs. Use --auth-profile <name> to select the reusable/API auth profile, --auth-mode <mode> to override config for one discovery run, and --refresh-auth to force a fresh state where the configured auth flow supports it. The resulting storage state is passed to the active driver session; discovery still receives only bounded, redacted page evidence.

Flags