> 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/creating-tests/new-test-from-here.md).

# New test from here

See how to avoid recording the same test steps multiple times. With BugBug you can duplicate them so that only part of the steps is copied over.

To avoid recording the same test steps multiple times you can duplicate them so that only part of the steps is copied over.

This is useful if you want to test different variants of the same user flow or if you want to reuse your previously recorded [components](/editing-tests/components.md).

{% hint style="info" %}
**Important!** "New test from here" action is not available between individual steps of a group. Use it before or after a group, so between the groups.
{% endhint %}

See the image below - all the groups below the purple line will be removed in the newly duplicated test.

![](https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2F0F41y9SC5VxumIDYhDBJ%2FScreenshot%202022-04-07%20at%2017.11.41.png?alt=media\&token=d18c2319-967e-4bdf-bfd1-c75564b64f0b)


---

# 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/creating-tests/new-test-from-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.