> For the complete documentation index, see [llms.txt](https://docs.askyazi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.askyazi.com/study-types/test-your-study.md).

# Test your study

Test a study before launch with the Test Simulator, the reusable test link and Run Simulation, and keep test data out of your results.

Always test a study before real participants see it. Yazi gives you three ways to test, each catching different problems, and keeps test answers separate from real ones.

{% hint style="info" %}
**In short:**

* **Test Simulator**: a phone preview inside Yazi. Fast for checking questions, logic, Flow screens and translations. Test voice notes and media on a real phone.
* **Test link**: run the real study on your own phone in WhatsApp, as many times as you like. Test answers are marked as test data.
* **Run Simulation**: AI-generated participants answer your study so you can see which logic paths get used and how the results look. Nothing is sent to anyone.
  {% endhint %}

## Which test to use

|                        | Test Simulator                                | Test link (your phone)                                        | Run Simulation                                     |
| ---------------------- | --------------------------------------------- | ------------------------------------------------------------- | -------------------------------------------------- |
| Where                  | In the Yazi web app                           | In WhatsApp on your phone                                     | In the Yazi web app                                |
| Best for               | Wording, routing, Flow screens, each language | The real participant experience, media answers, AI interviews | Logic coverage, screeners, a first look at results |
| Voice notes and media  | Not reliable, test on a phone                 | Yes                                                           | Simulated                                          |
| Multi-activity studies | One activity at a time                        | Starts at the first activity                                  | Walks every activity                               |
| Data                   | Marked as test data                           | Marked as test data                                           | Marked as simulated                                |

A good routine: check each activity in the Test Simulator, run the whole study on your phone with the test link, run a simulation to check routing and screeners, then ask a colleague to take it cold.

## Test Simulator

Open it with the **Test** button at the top right of the **Build** tab (it is also on the **Share** tab). A **Test Simulator** side panel opens with a phone preview of the WhatsApp chat, which starts with "Starting test session…". You answer by tapping, typing in the phone's message box or recording. Two buttons sit with it: **Run Simulation** (see below) and **Reset**, which starts a fresh test session.

The simulator shows your study as a participant would see it:

* **Real formats.** Questions that go out as WhatsApp Flows (including matrix and multi-select forms) appear as the actual Flow screens, with **Next** and **Back**, conditional screens and the submit screen.
* **Languages.** For a multi-language study, the first message asks which language you want, exactly as a participant sees it. The rest of the study runs in the language you pick, including the simulator's buttons and instructions.
* **Logic.** Routing, "Only show if" conditions and screen-outs behave as they will on WhatsApp.
* **Tap, do not type, on options.** When a question shows options, the message box is switched off and the simulator tells you to tap an option.

<figure><img src="https://358667285-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzMRQUXiGQlBwWdg6WEmG%2Fuploads%2F0WOHBciWcNBNXTjNBiMN%2Ffs-test-simulator.webp?alt=media&amp;token=a3cf82df-e3bf-411f-966e-5a52f9e78ae9" alt="The Test Simulator beside the builder: a phone preview of the study on WhatsApp, with Run Simulation and Reset"><figcaption></figcaption></figure>

**Limits of the simulator**

* The composer lets you record, but the simulator is not a true test of media. Test voice note, photo and video questions on a real phone.
* It runs one activity at a time and cannot stand in for the full journey of a multi-activity or diary study.

## Test link

The test link runs your real study on your own phone in WhatsApp. Find it on the **Share** tab. Every study gets one automatically, so there is nothing to switch on.

* Use it as many times as you like.
* Answers are marked as test data, so they never reach exports, reports or shared results links.
* **For AI interviews, always use the test link.** It resets the interview's memory each time. On the live link the AI remembers your earlier conversation, and if you already reached the question limit it will not ask you anything more.

To clear your own answers and start again from the beginning, send the study's starter phrase with **-TEST** added to the end. This clears the session for your number.

### Testing a multi-activity study end to end

Links to individual activities do not work while a study is in **Testing**, so testers always start at the first activity. To run the whole journey without waiting for real unlock times:

1. Temporarily set each activity to **Right away · 0–5 mins** (click the timing chip between activities).
2. Run the study end to end on your phone.
3. Restore the real unlock schedule, check the dates, and re-enable any scheduled broadcasts before you go live.

See [Multi-activity studies](https://docs.askyazi.com/study-types/multi-activity-studies.md).

## Run Simulation

Run Simulation creates AI participants (personas) who answer your study, so you can check logic and screeners at scale before any real person is involved. Start it with the **Run Simulation** button in the **Test Simulator** panel.

* **Simulated participants follow your screening rules**, so most qualify rather than being screened out at the first question.
* **They walk the whole study**, including every activity of a multi-activity study, matrix questions and WhatsApp Flow screens built as they would be on a phone.
* **Logic coverage** shows which routes the run used, so you can spot paths nobody reached. You can look back at past runs.
* **Results.** Simulated participants appear in the **Participants** view as completed and in the results table, with a switch to hide them. Any export that includes them has a **Simulated** column.
* **Nothing is sent to anyone.** A run with about 20 personas takes around 10 minutes.

**Error 429.** If a run stops with a 429 error, the AI service briefly limited how many answers could be generated at once. It is not a problem with your study. Wait a moment and run again, or run fewer simulated participants.

## Test data in your results

Test link and simulator answers are always labelled as test data. They never end up in an export, a report or a shared link.

* On **Responses** and **Reporting**, a test-data chip (for example "20 test") shows how many test responses exist. Switch it on to include test responses in the table, charts, Media Library and counts; switch it off to hide them all. Yazi remembers your choice per study.
* A study in **Testing** status shows its test data by default.
* Simulated respondents can be removed on their own, without touching a real participant. See [Clearing results before go-live](#clearing-results-before-go-live).

### Clearing results before go-live

If real responses were collected during testing (for example colleagues using the live link), clear them before fieldwork. When you clear results, Yazi asks what you want:

* **Clear results only** (selected by default) deletes answers but keeps each participant's progress through the study.
* A **full reset** also clears progress and queued messages. It tells you how many people it affects.
* **Remove simulated respondents only** clears simulated participants and nothing else.

## Pre-launch checklist

* Every question reads well on a phone, with no builder warnings.
* Routing, "Only show if" conditions and screen-outs send people where you expect.
* Every language has been run once in the simulator.
* Media questions have been answered on a real phone.
* AI interviews have been tested at least three ways: cooperative, low-effort and off-topic. See [AI interviews](https://docs.askyazi.com/study-types/ai-interviews.md#testing-an-ai-interview).
* Multi-activity studies: the full journey works and the real unlock schedule is restored.
* Invite, reminder and between-activity templates are approved in every language.
* Test data is hidden or removed.

## Limits and things to know

* **Test media on a real phone,** not in the simulator.
* **Deleting individual test transcripts.** Test transcripts on **Responses > Transcripts** show a delete icon when you hover over them. On a multi-activity study, deleting a transcript also resets that participant's progress. The dialog tells you what it will do before you confirm.
* **Individual activity links do not work in Testing.** Testers start at the first activity.
* **Simulated answers are not real answers.** Use simulations to check logic and set-up, never as data.

## Related

* [Publish and go live](https://docs.askyazi.com/study-types/publish-and-go-live.md)
* [Study links](https://docs.askyazi.com/reach-participants/study-links.md)
* [Multi-activity studies](https://docs.askyazi.com/study-types/multi-activity-studies.md)
* [Results overview](https://docs.askyazi.com/results-and-reporting/where-your-results-live.md)
