> 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

Use **Run and pause here** to run a test up to a chosen point and pause it there. This saves time when you want to fix or record steps in the middle of a long test.

The test runs locally, in a new browser window opened by the BugBug extension.

## Run and pause at a chosen point

1. Open the test.
2. Hover over the line between two steps where you want the test to pause, and click **+**.
3. Choose **Run and pause here**.
4. BugBug opens the test execution window and runs all steps up to that point.
5. The test pauses before the next step, and the paused mode starts.

{% hint style="info" %}
**Run and pause here** isn't available above the first step of the test, because there is nothing to run before it.
{% endhint %}

<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>

## What you can do in paused mode

When the test is paused, use the buttons in the test header:

* **Run next step and pause** - run one step and pause again
* **Resume** - continue the test to the end
* **Record** - record new steps from the current position
* **Stop** - stop the test

You can also click **+** between steps. In paused mode, the menu offers:

* **Record from here** - record new steps at this point
* **Set playback here** - move the playback position to this point without running anything
* **Resume from here** - continue the test from this point
* **Resume and pause here** - continue the test and pause again at this point

You can also edit steps while the test is paused. Read more in [Edit & Rewind](https://docs.bugbug.io/workflow-tips/edit-and-rewind.md).

## Breakpoints

A breakpoint makes the test pause at the same point every time you run it locally, so you don't have to choose **Run and pause here** again.

1. Hover over the line between two steps and click **+**.
2. Choose **Add breakpoint**.

The breakpoint is shown as an icon at that point. When a local run reaches it, the test pauses and the paused mode starts.

To remove a breakpoint, click its icon, or click **+** at the same point and choose **Remove breakpoint**.

{% hint style="info" %}
Breakpoints need BugBug extension version 12.47.0 or newer. With an older extension, the option isn't shown.
{% 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://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.
