> For the complete documentation index, see [llms.txt](https://help.craftsmanplus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.craftsmanplus.com/play/properties/dynamic-content/previewing-and-testing.md).

# Previewing & Testing

The **Preview** and **Share Link** both include dropdown menus for testing your dynamic layers. A menu appears for each condition category used in the project, letting you switch between conditions in real time and confirm every variant displays correctly.

***

### Condition Menus

Open a menu and select an option to simulate that condition. The playable updates immediately, showing the layers that match your selection and hiding the ones that don't.

Each menu also includes a **Fallback** option so you can verify what viewers see when nothing matches. See [Fallback](https://help.craftsmanplus.com/play/properties/dynamic-content/fallback.md).

A few behaviors to be aware of:

* The Preview opens in the same dynamic state you were viewing in the editor.
* All menus automatically select an option if you haven't assigned one, matching how these conditions always resolve to a real value on a viewer's device.
* Changing a condition restarts the current scene rather than the entire playable, so you can test variants without replaying from the beginning each time.
* The **Restart** button replays the playable using your current menu selections. Reloading the Preview or Share Link entirely resets the menus.

{% hint style="info" %}
*Template previews also include the condition menus, so dynamic behavior can be tested before a template is used.*
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.craftsmanplus.com/play/properties/dynamic-content/previewing-and-testing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
