> For the complete documentation index, see [llms.txt](https://docs.testery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testery.io/integrations.md).

# Integrate with Testery

- [Built-In Integrations with Testery](https://docs.testery.io/integrations/built-in-integrations-with-testery.md)
- [Jira](https://docs.testery.io/integrations/built-in-integrations-with-testery/jira.md): Testery's built-in Jira integration allows user to create stories for errant tests and bugs found while testing. Stories can be tied to individual or groups of tests.
- [Slack](https://docs.testery.io/integrations/built-in-integrations-with-testery/slack.md)
- [CI/CD Integration Guides](https://docs.testery.io/integrations/ci-cd-integration-guide.md)
- [Azure Devops Pipelines](https://docs.testery.io/integrations/ci-cd-integration-guide/azure-devops-pipelines.md)
- [Set Up CircleCI to Run Testery Tests](https://docs.testery.io/integrations/ci-cd-integration-guide/circleci.md): How-to trigger a Testery test run from a CircleCI build.
- [Jenkins](https://docs.testery.io/integrations/ci-cd-integration-guide/jenkins.md): Configure Jenkins in minutes to run your end-to-end tests concurrently via Testery Cloud
- [GitHub Actions](https://docs.testery.io/integrations/ci-cd-integration-guide/github-actions.md)
- [Octopus Deploy](https://docs.testery.io/integrations/ci-cd-integration-guide/octopus-deploy.md)
- [TugboatQA](https://docs.testery.io/integrations/ci-cd-integration-guide/tugboatqa.md): Using Tugboat and Testery is one of the coolest, easiest, and fastest ways to run your E2E Cypress tests on every PR. Follow these four steps and in about 10 minutes, you'll have Cypress tests running
- [Testery CLI](https://docs.testery.io/integrations/testery-cli-docs.md)
- [Testery REST API](https://docs.testery.io/integrations/testery-rest-api.md)
- [Testery REST API Resources](https://docs.testery.io/integrations/testery-rest-api/testery-rest-api.md): A description of the available Testery REST API end points.
- [Microsoft Teams](https://docs.testery.io/integrations/microsoft-teams.md)
- [Testery MCP Server](https://docs.testery.io/integrations/testery-mcp-server.md)
- [Claude Plugin](https://docs.testery.io/integrations/testery-claude-plugin.md)


---

# 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.testery.io/integrations.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.