Run a Test Case
Overview
Section titled “Overview”Launch one test case variant through an agent harness and watch it to completion. The console enqueues the run at the backend, which executes it as a per-run driver Job. The CLI inspects the inputs a run is given without contacting anything.
Prerequisites
Section titled “Prerequisites”- A reachable console whose backend queue an in-cluster
dispatcher is draining: a deployment’s
console.testcabinet.ai, reached through Cloudflare Access, or the local k3d service stack. - Harness credentials configured in that deployment (Set Up Authentication). The launching machine needs no container runtime and no provider key of its own.
Run it
Section titled “Run it”In the console, open the case’s page, pick the version and the variant, choose the harness and the model, and start the run. A run targets exactly one variant, and the model is passed to the harness unchanged. The launch form’s optional settings:
- The maximum runtime overrides the case’s
max_runtime_hoursfor this run. Fractional hours are accepted, for example0.5. - The authentication mode (
auto,subscriptionorapi-key) selects how the harness authenticates for this run. - The retry count sets how many times the backend retries the run after a
terminal infrastructure error. The default is one retry;
0disables retries. - The orchestrator selects what conducts the harness sessions. It defaults to
one-shot; see Orchestrators. - The engine selects the engine the produced
build is written against, one the case supports. It defaults to
none.
The console shows the queued job, streams the live event stream as the driver seeds the repository, drives the harness, and validates the result, then shows the run record summary.
Inspect the inputs without a run
Section titled “Inspect the inputs without a run”From the microservice-driver checkout, or with a released tcab:
tcab prompt --test-case carom --version v1.0.0 --variant base # the rendered prompttcab seed --test-case carom --version v1.0.0 --variant base # the seeded repo, on diskThese read the test-suites checkout and contact nothing. From source,
substitute cargo run -p test-cabinet-driver --bin tcab -- prompt … for
tcab prompt ….
Next steps
Section titled “Next steps”- Review a Run once it finishes.
- Reviewing Test Run Results for the full review workflow.