Run and Verify

Execute tests and retrieve results. Pairs naturally with Group 5 - heal, then re-run to confirm - and with Group 3 - adjust an assertion, then re-run to verify.

run_functional_tests RUN

Starts a background test run scoped to a project, suite, or case. Returns a runId.

Key parameters:

  • project*, testSuite* - optional: testCase

Try asking your AI client: "Run the Payments Smoke Tests suite."

job_status_poll RUN

Polls the status of a running job. Returns status (RUNNING, COMPLETED, FAILED, CANCELED), percent complete, pass/fail/pending summary, and nextPollAfterMs. Supports long-polling by using waitSeconds (0–20) - the server holds the request and returns early when the job finishes, reducing the round-trip time. Call again after nextPollAfterMs until status is no longer RUNNING.

Key parameters:

  • runId* - optional: waitSeconds

job_result_read RUN

Fetches full per-case and per-step results for a completed job. Only available once job_status_poll reports COMPLETED or FAILED. For targeted failure logs only, use job_failures_read instead.

Key parameters:

  • runId*

Try asking your AI client: "Show me the results of that last test run - what failed and why?"

job_failures_read RUN

Fetches targeted log lines for failed test items within a completed job. Use this for focused root-cause analysis without retrieving the full result set.

Key parameters:

  • runId*

Try asking your AI client: "Show me only the failures from that last run."

See Also

Publication date: