> For the complete documentation index, see [llms.txt](https://docs.aqua-cloud.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aqua-cloud.io/documentation/desktop-client/test-management/step-designer.md).

# Step Designer

Design and organize test steps efficiently with the Step Designer in the desktop client. Streamline your test management workflow for improved accuracy and clarity.

The step designer allows to create steps and conditions to create manual test steps and to extend it with automated tests.  

<figure><img src="http://aquawiki.andagon.com/pictures/drex_step_designer_rich_client_custom.png" alt=""><figcaption></figcaption></figure>

A default test condition and a test step are available. *Conditions* have an instruction field that can be specified, and *Steps* has an *Instructions* field and *Expected results* field. These fields are full rich text fields that can be specified with known Microsoft Word functionality. By clicking on *Detailed entry,* you receive a better view to specify test cases. By clicking on the tabs *Text* or *Table*, you receive full rich text functionality where you can insert images, tables, and text for manual test execution.&#x20;

<figure><img src="http://aquawiki.andagon.com/pictures/drex_step_designer_rich_client_custom_2.png" alt=""><figcaption></figcaption></figure>

You can specify the test case as follows: &#x20;

<figure><img src="http://aquawiki.andagon.com/pictures/drex_step_designer_rich_client_custom_3.png" alt=""><figcaption></figcaption></figure>

By clicking on Close Step Designer, you return to the main test case and have the option to execute the test case.&#x20;

Check the video about test steps in aqua

{% embed url="<https://www.youtube.com/watch?ab_channel=andagon&v=7FAcQ2yKlOI>" %}


---

# 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.aqua-cloud.io/documentation/desktop-client/test-management/step-designer.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.