> 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/duplicating-tests.md).

# Duplicating tests

See how to duplicate your tests with BugBug without a need to create them from scratch.

You don't need to create tests from scratch. Duplicate an existing test and then edit the copy. To copy only the first part of a test, use [New test from here](/creating-tests/new-test-from-here.md).

## How to duplicate a test

You can duplicate a test:

* **from the tests list** - open the **...** menu in the test's row and choose **Duplicate**
* **from the test page** - open the test's actions menu and choose **Duplicate**

BugBug asks for the name of the duplicated test. The name must be different from the names of other tests in the project.

![Duplicate from the tests list](https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2F9ElCY6D9mb8bpNzLpOgD%2FScreenshot%202022-04-07%20at%2016.50.17.png?alt=media\&token=74d8fb79-7785-4b47-ab89-c0ec4035f613)

![Duplicate from test details](https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FdRmNtJJEg3zKpCVZiipz%2FScreenshot%202022-04-07%20at%2016.43.30.png?alt=media\&token=29fa5b33-3ddd-444c-bf18-592ee98f537f)

## What the copy contains

The duplicated test has:

* all the steps and groups of the original test
* the same [components](/editing-tests/components.md). Components are shared, not copied, so a change in a component affects both tests
* the same tags, folder, profile and screen size

The copy doesn't have the run history of the original test. It's added to suites that automatically include new tests, such as **All tests**, but not to the other suites of the original test.


---

# 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/duplicating-tests.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.