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.

webtest-ai run

Runs one Markdown suite file or a directory of suite files through the WebTest AI parser, interpreter, execution driver, and reporters.

webtest-ai run --suite specs/homepage.md
webtest-ai run --suite specs --tags smoke
webtest-ai run --suite specs/checkout.md --target brand-b-fr
webtest-ai run --suite specs --exclude-tags serial --workers 4

The candidate defaults to bounded execution and native CDP Chromium. Goal specs need agent.profile; exact-step specs can run without navigator inference. A custom target must exist in config.targets. Run from your own project, not inside the installed package.

Trace and journey flags are retained for legacy execution; they do not enable those features in the bounded engine. Non-Chromium browser aliases require a compatible driver and are not covered by the bounded Chromium validation.

Flags

Output

The command prints suite counts, status counts, run ids, and report paths. JSON and HTML reports are written under artifacts/reports/; per-test artifacts are written under artifacts/<runId>/<testId>/.

The process exits nonzero for failed, inconclusive, or blocked results, and for command/configuration errors. Inspect skipped counts separately; a successful process exit is not proof that every selected test executed.