> For the complete documentation index, see [llms.txt](https://docs.gpmautomate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gpmautomate.com/automate-en/general-introduction/test-action-guide.md).

# Test action guide

Testing is an important step that helps you control the flow of the script, allowing you to run each step or block of commands to ensure everything operates as intended before actual execution.

### 🎯 Why Test Action?

* Error control: Detect and address issues as actions are performed, rather than having to run the entire script from the beginning.
* Flexible tuning: You can isolate a single action or a block of commands for testing, which helps shorten debugging time.
* Test as you go: GPM Automate supports direct testing on GPM Login profiles, allowing you to observe results immediately in the browser.

> Note: The Test feature currently only supports profiles in GPM Login.

### ⚙️ Testing Procedure

To start the testing process, follow these steps:

#### 1️⃣ Step 1: Configure Profile in GPM Login

* Open GPM Login.
* Locate the profile you want to use for testing.
* Click on the three dots next to the profile name.
* Select Run with remote port to obtain the control port information.

<figure><img src="/files/3z8gtJrBD348yeebQ7YF" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/gFW9RSGROuEansMUYgEn" alt=""><figcaption></figcaption></figure>

#### 2️⃣ Step 2: Set Up in GPM Automate

* In the GPM Automate interface, select the action or block of commands you want to test.
* On the toolbar above, click the Test button.
* A Test configuration dialog will appear.
* Enter the Port obtained from GPM Login in Step 1 into the corresponding field.
* Click Start to begin.

<figure><img src="/files/bxNnk3AODQdonA2NqoSN" alt=""><figcaption></figcaption></figure>

#### 3️⃣ Step 3: Observe Results

* After clicking Start, the system will execute the command on the selected profile.
* You can monitor the results displayed in the browser window and the log of GPM Automate to adjust the script if necessary.


---

# 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://docs.gpmautomate.com/automate-en/general-introduction/test-action-guide.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.