Skip to main content
TestDino integrations connect your CI/CD, issue tracking, and communication tools to test run data. Each one posts results, creates tickets, or answers questions in the tool your team already works in.

Available Integrations

github-svgrepo-com

GitHub App

PR comments, CI checks, PR dashboard sync
gitlab-logo-500-rgb

GitLab

MR comments, merge request dashboard sync
azure-devops

Azure DevOps

View test runs inside Azure DevOps
jira-icon

Jira

Create issues from failed or flaky tests
jira-icon

Jira Forge App

View linked test cases, runs, and sessions inside Jira issues
linear

Linear

Create issues from failed or flaky tests
asana

Asana

Create tasks from failed or flaky tests
mon

monday

Create items from failed or flaky tests
slack

Slack App

Run summaries + annotation-based failure alerts
slack

Slack Webhook

Custom webhook notifications
openclaw-color

OpenClaw Chat Bot

Query TestDino from Slack, Telegram, Discord, WhatsApp
n8n

n8n

Trigger workflows on test runs, query data with the community node

Connection Scope

CI/CD Integration

These are app-level connections that sync data between TestDino and your Git provider. Once connected, they post test summaries, run CI checks, and sync pull request or merge request data into TestDino automatically.
Looking to upload test results from your CI pipeline? That’s covered in CI Setup under Getting Started. Integrations here are for app connections that sync data and post feedback.

Issue Tracking

Create bug tickets directly from failed or flaky tests in TestDino. Each ticket includes prefilled context: test name, file, error message, failure history, console logs, and links to the TestDino run and Git commit.

Communication

Route test run notifications to your team’s chat, and ask TestDino questions in plain language without opening the dashboard.
A project can hold many Slack notifications at once, so a run summary in a team channel and a failures-only alert to an on-call user are 2 separate notifications. Use an annotation-based notification to reach the owner named in your test code. See Annotations Guide.

Automation

Connect no-code workflows to test runs through n8n. Trigger automations when a run starts or finishes, then read test runs, test cases, specs, analytics, and usage downstream.
Last modified on September 9, 2026