> For the complete documentation index, see [llms.txt](https://bugowl.gitbook.io/bugowl-ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bugowl.gitbook.io/bugowl-ai/core-concepts/steps-tasks.md).

# Steps/Tasks

Test Steps (also called Test Tasks) are the individual actions and validations that make up a test case. They define what the test should do step by step, using natural language that AI can understand and execute.

#### What are Test Steps?

Test steps contain:

* **Step Description**: Natural language description of what to do
* **Test Data References**: Variables from test data using @syntax
* **Execution Order**: Sequential steps that run in order
* **Live Execution**: Real-time browser automation with visual feedback

#### Creating Test Steps

1. Go to a test case and click "Edit Steps"
2. Write each step in natural language
3. Use @testDataName to reference test data variables
4. Drag steps to reorder them
5. Use "Edit All" for bulk editing multiple steps
6. Save as draft or finalize when ready

#### Step Writing Tips

**Natural Language Examples:**

* "Click the login button"
* "Enter @userCredentials in the email field"
* "Verify the welcome message appears"
* "Navigate to the checkout page"

**Test Data Integration:**

* Use @syntax to reference test data: @userCredentials
* Test data values are automatically substituted during execution
* Click on @tags to see the actual data values

#### Step Execution

**Individual Steps:**

* Click the play button next to any step
* Watch live execution in the browser view
* See real-time status updates

**All Steps:**

* Click "Run All" to execute all steps sequentially
* Use Pause/Resume to control execution
* Stop execution at any time

#### Live Browser View

The test task editor includes a live browser view that shows:

* **Real-time execution**: See steps being performed live
* **Browser controls**: Back, forward, refresh navigation
* **Current URL**: Shows the page being tested
* **Connection status**: Green dot indicates live connection

#### Step Management

* **Add Steps**: Click "Add new step" to create additional steps
* **Reorder Steps**: Drag the grip handle to reorder steps
* **Delete Steps**: Click the X button to remove steps
* **Bulk Edit**: Use "Edit All" to edit multiple steps at once

#### Saving and Finalizing

* **Save as Draft**: Saves steps but keeps test case as draft
* **Finalize**: Makes test case ready for execution (published)
* **Auto-save**: Steps are automatically saved as you work

#### Visual Feedback

During execution, you'll see:

* **Running**: Blinking border around active step
* **Completed**: Green checkmark for successful steps
* **Failed**: Red indicator for failed steps
* **Waiting**: Hourglass for queued steps

This live execution environment makes it easy to create, test, and refine your test steps with immediate visual feedback.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://bugowl.gitbook.io/bugowl-ai/core-concepts/steps-tasks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.