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

# Test and publish a study

> Check questionnaire routes, run participant tests, and publish the saved questionnaire and recruitment setup.

Testing combines an automated route check with manual participant sessions. Complete both before publishing, especially when the study contains screening, jumps, randomization, translations, concepts, or custom-code questions.

## Before you start

Save the questionnaire and prepare the final audience, translations, consent wording, and provider configuration.

## Run Flow coverage

In **Create**, open the builder view menu and select **Test**. Under **Flow coverage**, select **Run check**.

<Frame caption="The Test view contains Flow coverage and the test-link controls.">
  <img src="https://mintcdn.com/deepfieldai/dK8nllvOe0f0oG_-/images/recruiting/test-view.png?fit=max&auto=format&n=dK8nllvOe0f0oG_-&q=85&s=c3a3224be9475aead55b0a06fc5247a6" alt="Test your survey view with Flow coverage and Generate test link sections" width="1440" height="900" data-path="images/recruiting/test-view.png" />
</Frame>

Flow coverage evaluates conditions, screening rules, jumps, end-survey rules, and variables to identify unreachable questions or incomplete routes. Open each reported issue and correct the referenced logic. Run the check again after saving.

## Generate a test link

Select **Generate test link**. The current form is saved and published for testing, and the study moves from Draft to Testing. Use **Open** to start a session or **Copy** to share it with reviewers.

Test sessions do not count as live panel completes. To focus on one question and its dependencies, open that question's menu and select **Test this question**.

Test at least:

* A normal qualifying completion.
* Every screen-out and early-end route.
* Each language.
* Boundary answers used by conditions and validation.
* Randomized or concept-loop variants.
* Custom-code questions on desktop and mobile widths, including a reload after answering.
* Redirect behavior when a provider is involved.

<Warning>Saving a questionnaire change in Testing displays **Disable Test Mode?**. Confirming returns the study to Draft and invalidates all existing test links. Generate and distribute a replacement link after the changes are saved.</Warning>

<Frame caption="The generated test link offers Copy and Open controls. Run the flow check as well as the participant test.">
  <img src="https://mintcdn.com/deepfieldai/dK8nllvOe0f0oG_-/images/recruiting/test-link-generated.png?fit=max&auto=format&n=dK8nllvOe0f0oG_-&q=85&s=538324590cd266566fb1a467e362ffeb" alt="Test view with a generated participant link, Copy and Open buttons, and the flow-check control" width="1440" height="900" data-path="images/recruiting/test-link-generated.png" />
</Frame>

## Invite one participant directly

When the study is Published, select **Invite** on Fieldwork. Enter the participant's email and select **Generate Link**. Share the unique URL and note its displayed expiry date.

The link can reopen an unfinished response within its allowed sessions. It stops accepting entries when the response is complete or the link expires.

For provider traffic, use the panel invite workflow described in [Configure a panel-provider link](/recruiting/panel-links).

## Publish

<Steps>
  <Step title="Resolve launch blockers">
    Save or undo all questionnaire changes. Complete and save every translation. Confirm the panel and quota configuration.
  </Step>

  <Step title="Open Fieldwork">
    Review the coding fees, the recruiting estimate for any panel DeepField recruits, and the launch summary. Check the sample-size estimate in **Create → Quotas, panels & links**.
  </Step>

  <Step title="Select Publish">
    Read the **Publish Survey** confirmation. Use **Open Test** if another participant review is required.
  </Step>

  <Step title="Confirm submission">
    Confirmation moves a Draft or Testing study directly to **Published**. It can then accept live participants.
  </Step>
</Steps>

## Understand status changes

| Status        | Available work                                                                          |
| ------------- | --------------------------------------------------------------------------------------- |
| **Draft**     | Edit the complete setup, use the assistant, and restore versions.                       |
| **Testing**   | Use active test links; form changes require returning to Draft.                         |
| **Published** | Live participants can enter; safe live edits and recruitment controls remain available. |
| **Completed** | New responses stop; response review and analysis remain available.                      |

## Troubleshooting

<AccordionGroup>
  <Accordion title="A test link no longer works">
    The study returned to Draft after an edit, assistant action, or version restore. Open **Test** and generate a new link.
  </Accordion>

  <Accordion title="Publish is unavailable">
    Hover the control and check the launch summary. Resolve pending form changes, out-of-date translations, validation problems, or incomplete panel settings.
  </Accordion>

  <Accordion title="The participant does not see the DeepField completion screen">
    A **Success Redirect URL** is configured for the panel or provider. Clear it if the built-in completion screen should be used.
  </Accordion>
</AccordionGroup>

## Check the result

Keep a record of the tested routes and outcomes. Confirm the study reaches Published before sending live traffic.

## Related

* [Configure a panel-provider link](/recruiting/panel-links)
* [Configure your audience](/recruiting/panels-demographics)
* [Translate your survey](/translations/multilingual-studies)
* [Monitor responses](/responses/monitoring-responses)