> For the complete documentation index, see [llms.txt](https://docs.opsmx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opsmx.com/opsmx-1/opsmx-context-engine/user-guide/manage-pipelines/add-intelligent-gates-to-the-pipeline/test-verification-gate.md).

# Test Verification Gate

### Test Verification Gate

An approval gate stops the pipeline and waits for approval either from a human user or from a computer based on data from a supported plugin.

You can add a **Test Verification** Gate after creating a pipeline to the application. To add a **Test Verification Gate** follow the steps below:

If you haven’t created an application already,  click [**here**](https://docs.opsmx.com/release-history/previous-releases/isd-4.0/knowledgebase/manage-application/create-an-application).

If you haven’t created your pipelines yet, click [**here**](https://docs.opsmx.com/release-history/previous-releases/isd-4.0/knowledgebase/manage-pipelines/create-a-pipeline).

1. From the [**Application dashboard**](https://docs.opsmx.com/user-guide/dashboard/application-dashboard), select your application name which you need to edit a pipeline. Click **Three dots** at end of the application name and then select [**Edit Pipeline**](https://docs.opsmx.com/user-guide/manage-pipelines/edit-pipeline) as shown in the image below.

![](/files/viINanxAwLDSFIqnpnmA)

2\.  The **Pipelines** page appears, where you need to add the Approval Stage. Click [**Add Stage**](https://docs.opsmx.com/user-guide/manage-pipelines/add-stage)**,** select **Test Verification** from the **Type** drop-down as shown in the image below.

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

3\.  The **Test Verification Configuration** page appears. You need to configure the test verification gate with the attributes as shown in the image below.

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

**Test Verification configuration attributes**&#x20;

* **Gate URL**: Please enter the Gate URL
* **Life Time Hours**: Please enter the Life Time in Hours like 0.5
* **Minimum Canary Result**: Please enter the Minimum Canary Result
* **Canary Result Score:** Please enter the Canary Result Score
* **Log Analysis**: Please Enable Log Analysis with true / false
* **Baseline Start Time:** Please select Baseline Start Time
* **Canary Start Time**: Please select Canary Start Time
* **Test Run Key:** Please enter the Test Run Key
* **Baseline Test Run Id:** Please enter the Baseline Test Run Id
* **New Test Run Id:** Please enter the New Test Run Id
* **Test Run Info:** Please enter the Test Run Info
* **Gate Name:** Please enter Gate Name that is created in OES
* **Image Ids:** Please enter the Image IDs

4. Click **Save changes** and the Test Verification Gate is added to your pipeline.


---

# 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.opsmx.com/opsmx-1/opsmx-context-engine/user-guide/manage-pipelines/add-intelligent-gates-to-the-pipeline/test-verification-gate.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.
