> For the complete documentation index, see [llms.txt](https://docs.bugbug.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugbug.io/running-tests/run-and-pause-here.md).

# Run and pause here

If you want to run a test to a certain point, you can easily do this with the `Run and pause here` option.

To use this function, you have to:

1. Hover on a step you want to run to.
2. Click `+` icon.
3. Click `Run and pause here` option.
4. The test execution window will open, and the test will run until the given step.
5. The paused mode will activate, and you can continue running step-by-step or resume a test execution.

<figure><img src="https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FzL5T57SlFaB7E79FeykE%2Fimage.png?alt=media&amp;token=99b7ec2e-46b5-4fc7-bf5d-a809e87061ae" alt=""><figcaption><p>Run and pause here in the webapp UI</p></figcaption></figure>

<figure><img src="https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FkJKh6cThWS6zLfJMURxQ%2Fimage.png?alt=media&amp;token=f8b9380d-eb92-47c3-b1a2-2a29c047add5" alt=""><figcaption><p>Test execution window with option to resume running or run step-by-step</p></figcaption></figure>

When the test is paused, you can record new steps, change the playback position, resume execution, or modify steps from the UI. BugBug gives you a lot of control. Read more about it on the page [Edit & Rewind](/workflow-tips/edit-and-rewind.md).


---

# 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://docs.bugbug.io/running-tests/run-and-pause-here.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.
