# DevOps The DevOps Integration functionality allows you to log defects and other issues on DevOps based on reports generated by Avo Assure. #### Different execution trigger types in DevOps {% hint style="info" %} To learn more about DevOps Intergration, refer to[ DevOps Integration](https://docs.avoautomation.com/integrations-in-avo-assure/devops-integration) {% endhint %} **A. HTTP Request** HTTP Request is used when a test case requires communication with external web services or APIs, like RESTful. It enables you to send HTTP requests and validate the responses, making it possible to automate scenarios where system-to-system interaction is necessary. **B. Code snippet** Code snippet is helpful when custom logic is needed beyond the available built-in actions. You can embed and run small scripts or code blocks in various programming languages directly within your test workflow, allowing flexibility to handle complex scenarios. **C. Cloud Execution** Cloud Execution supports running automated tests in cloud-based environments rather than on local machines. In Avo Assure, Cloud Execution currently supports **Harness** and **Docker** as execution triggers. It enables scalability, cross-browser/device testing, and reduces dependency on local infrastructure. ## **A. HTTP Request** Below are the steps to trigger execution using HTTP request: 1. On the **Execution** tab, select parent folder. 2. Select **DevOps** from the top right corner and the **DevOps** pop-up appears.
3. Select **HTTP Request** to send HTTP requests and validate responses when the Testcase requires interaction with external webservices or APIs. 4. Copy **DevOps Integration URL** and **DevOps Request body** from the **DevOps** window**.** 5. Select **Asynchronous** or **Synchronous**: 1. **Asynchronous:** Execution Responses are generated simultaneously during the execution. 2. **Synchronous:** Execution Responses are generated after the end of execution.
## **B. Code snippet** 1. Select parent folder and select **DevOps** from the top right corner. The **DevOps** pop-up appears.
2. Select **Code snippet** to add custom logic by embedding and running scripts within the test workflow, enabling handling of complex scenarios. 3. Enter the time in second in the **Set The Time**r to trigger the execution at the provided time. 4. Select the language form **Select Language.**

Note:

5. Select **Proxy** and provide **Proxy URL.** {% hint style="info" %} **Note**: By default, the **Proxy** option is disabled. By enabling, it allows you to provide a **Proxy URL**. {% endhint %}
## **C. Cloud Execution** 1. Select parent folder and select **DevOps** from the top right corner. The **DevOps** pop-up appears.
2. Select **Cloud Execution** and **copy** the code snippet containing the execution list details. {% hint style="info" %} **Note:** * You can Increase or decrease the **Parallel Count** as required for execution. * Cloud Execution supports two environments — **Docker** and **Harness**. * Copy and save both code snippets in a file (e.g., Notepad) for later use when triggering the execution on the cloud environment. {% endhint %}