> 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).
# 🛠️Testing action guide
Testing is an important step that helps you control the flow of your script, allowing you to run each step or block of commands to ensure everything operates as intended before the actual run.
🎥 Watch the tutorial video: [Here](https://youtu.be/zrX3ldxvEDE).
### 🎯 Why is it necessary to 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 to test, helping to shorten debugging time.
* Process as you go, test as you go: GPM Automate supports direct testing mechanisms 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 get the control port information.
#### 2️⃣ Step 2: Set up in GPM Automate
* In the GPM Automate interface, select the action or block that 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.
#### 3️⃣ Step 3: Observe the 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.gpmautomate.com/automate-en/general-introduction/test-action-guide.md?ask=&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.
