> For the complete documentation index, see [llms.txt](https://docs.testvibe.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testvibe.com/testvibe-api/core-concepts/runs-and-artifacts.md).

# Runs & artifacts

A **run** is one execution of a feature's generated Playwright tests, in an isolated cloud sandbox, against the project's URL (or a `siteUrl` override).

## Run lifecycle

Dispatching a run returns a `runId` immediately; the sandbox spins up and executes in the background.

| Status    | Meaning                                                                               |
| --------- | ------------------------------------------------------------------------------------- |
| `running` | Queued or executing in the sandbox.                                                   |
| `passed`  | Finished, every test passed.                                                          |
| `failed`  | Finished with failures — the digest carries per-test errors and a trimmed runner log. |

Typical wall-clock time is **\~30 seconds** for a small feature. Poll with [`get_run`](/testvibe-api/api-reference/runs/get_run.md) or block with [`wait_for_run`](/testvibe-api/api-reference/runs/wait_for_run.md) / `testvibe run … --wait`.

## The results digest

[`get_run`](/testvibe-api/api-reference/runs/get_run.md) returns a digest designed to be read by humans *and* AI tools:

```json
{
  "runId": 214,
  "status": "passed",
  "featureName": "Login Functionality",
  "config": "Default",
  "summary": { "total": 3, "passed": 3, "failed": 0, "other": 0 },
  "tests": [
    { "name": "Valid user signs in", "status": "passed", "durationMs": 4210, "error": null }
  ],
  "artifacts": [
    { "kind": "trace", "path": "trace/login.zip", "size": 482133 }
  ]
}
```

On failure, each failing test carries a trimmed `error`, and the digest includes a `log` excerpt from the runner.

## Artifacts

Runs upload Playwright **traces, screenshots, videos, and reports** to artifact storage. [`get_run_artifacts`](/testvibe-api/api-reference/runs/get_run_artifacts.md) exchanges the manifest for **short-lived signed download links**.

{% hint style="info" %}
Artifact URLs expire quickly by design — fetch them right before downloading, and don't persist them.
{% endhint %}

## Configurations

A run executes under a named [Playwright configuration](/testvibe-api/core-concepts/files-and-configurations.md) (`Default` unless you pass `config`) — that's where browser, viewport, and timeout choices live.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.testvibe.com/testvibe-api/core-concepts/runs-and-artifacts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.