> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/support-resources/tips-and-tricks/integrations.md).
# Integrations
Use this section to learn tips and tricks for working with Integrations. These help you connect external tools with the platform to enable automated test execution and support continuous testing in CI/CD workflows.
Integrate Avo Assure with CI/CD Pipelines
Integrate Avo Assure with CI/CD tools such as **Jenkins**, **Harness**, **Docker**, or **Azure DevOps** to automatically trigger test executions after each build or deployment, enabling faster feedback and continuous validation.
Enable Automatic Result Synchronization
Enable result synchronization with integrated test management and reporting tools to automatically update execution status and maintain consistent test tracking across platforms.
Generate Synthetic Test Data with GenRocket
Use **GenRocket** from the **Test Data Management** section under **Integrations** to generate synthetic test data dynamically, reducing manual effort and improving test data coverage across multiple test cases.
Update Test Data Using Runtime Data Parameterization
Use **Runtime Data Parameterization** in the **Execution List Configuration** to apply a new Excel dataset during execution without modifying parameterized test cases.
---
# 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.avoautomation.com/avo-assure/support-resources/tips-and-tricks/integrations.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.