> 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/editing-tests/manually-creating-the-test.md).

# Manually editing steps

BugBug allows users to manually edit test steps. Although this is not a recommended way of updating tests. It's often much faster to fix the tests by removing the failed steps and recording them again

Before you jump into manually editing, make sure you learn [how to re-record test steps](/recording-tests-steps/re-recording-steps.md), as this is a recommended way of updating your tests. It's often much faster to fix the tests by removing the failed steps and recording them again, rather than manually updating step settings.

## Manually adding steps

You don't need to use recording. You can also build a test step by step by adding actions and setting their parameters.

Hover over the line between two steps where you want to add something, and click **+**. The menu offers:

* **New step** - add an action, an assertion or a visual regression step
* **New assertion** - add an assertion
* **Add condition** - add an [if condition](/editing-tests/conditional-logic-if-else.md)
* **Paste** - paste steps you copied before
* **New group** - start a new group of steps
* **Insert existing component** - add a [component](/editing-tests/components.md) you already have

When you add a step, the **Add a new test step** window opens. Pick the step type on the **Actions**, **Assertions** or **Visual regression** tab.

![](https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FhCzAvhQrc6DallYjtFxs%2FScreenshot%202022-04-07%20at%2016.41.49.png?alt=media\&token=90844dd1-fe78-47a6-b6d2-b1239234ec97)

## Step details panel

Make your manual changes in the step details panel. Click a step to see all its parameters.

![](https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FjfPQZya5QULm80XbyCFr%2Fimage.png?alt=media\&token=4ce1c722-4a79-4c49-b884-8d73e200141f)

{% hint style="info" %}
**Important!** Don't forget to save your changes after editing a step.
{% endhint %}

{% hint style="success" %}
When editing the actions don't forget that you can use [variables](/editing-tests/variables.md).
{% endhint %}

## Operations on test steps

Open the **...** menu of a step to:

* **Duplicate** the step
* **Copy step**, to paste it somewhere else in this or another test
* **Copy link to step**
* **Deactivate step**, so it's skipped during runs, or **Activate step** again
* **Delete** the step

To run the test up to a chosen step and pause there, use [Run and pause here](/running-tests/run-and-pause-here.md) in the **+** menu.

### Working with several steps at once

Select several steps to **Copy**, **Activate**, **Deactivate** or **Delete** them together. Click **Deselect all** to clear the selection.

### Reordering steps

You can also drag steps to reorder them within the test:

![](https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FfjPrjvl0oFMVCdNOqSiw%2Fimage.png?alt=media\&token=765cc9e9-0cd3-4578-be9b-df8dd5d68595)


---

# 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/editing-tests/manually-creating-the-test.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.
