> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usertick.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Usertick runs surveys on websites, by link, by QR code and by email, and collects every response in one inbox with reports, dashboards and workflows. The REST API lives at https://app.usertick.com/api/public/v1 and uses Bearer API keys or OAuth access tokens; the JavaScript SDK is the @usertick/snippet package on npm.

# Test a workflow

> Run a workflow once on the survey's latest response before you publish it, and read what each step did: sent, checked, skipped or failed.

**Test run** runs the workflow once, right away, while you edit it, and Usertick saves any unsaved changes first.

## Run a test

**1. Open the test window**

In edit mode, select **Test run**.

**2. Run it**

Select **Run test**.

**3. Read the result**

The window lists each step the run reached and what happened there, and **Run again** runs the test once more.

You can't use **Test run** while the workflow has something left to fix. See [Publish and manage a workflow](https://docs.usertick.com/workflows/publish.md#publish-a-workflow).

## What a test does

* It runs on the survey's latest response, or on a sample response when the survey has none.
* Steps that post a message or create a record send a real one, labeled as a test. Other steps check the tool without adding data.
* **Assign to teammates** checks the teammates without assigning the response or notifying anyone, and the test skips the step on a sample response.
* A **Wait** doesn't hold the run, and the test skips steps under **With Zapier**.
* A test never appears in the workflow's **Activity**.

Each tool's guide says what its step does in a test.

## Outcomes

Each step in the result shows one of these outcomes:

* **Sent** means the tool accepted the send.
* **Checked, nothing sent** means the step checked the tool without writing anything.
* **Skipped** means the step had nothing to send for this response and the run went on, and the step shows the reason.
* **Failed** means the send failed and the run stopped there, and the step shows the error.
* **If yes** or **If no** shows the side an **If / else** took.
* **Not waited** marks a **Wait** that the test passed over.

## When no step runs

If the latest response doesn't meet the trigger's conditions, the window says "This response does not meet the trigger's conditions, so no step ran." To run the steps on that response regardless, select **Run anyway**.

For a [threshold alert](https://docs.usertick.com/workflows/threshold-alerts.md), the test measures the number as it is now, such as "The number is 27 now, and the line is 30.", and runs the steps only when the number is past the line, unless you select **Run anyway**.

An organization can start up to 10 test runs a minute.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.