Skip to main content
TestDino integrations deliver test result context directly into your CI/CD, issue tracking, and communication tools. Teams stay informed on every test run, act on failures immediately, and resolve issues faster without switching between platforms.

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

What Each Category Does

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.
TipLooking 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 Slack so your team stays updated without opening TestDino.
TipThe Slack App supports two alert types: run-level summaries (fires on every run) and annotation-based alerts (fires only when specific annotated tests fail). Use annotations to notify the right person for critical test failures. See Annotations Guide.

Automation

Query TestDino in plain language and build no-code workflows that react to test runs. Ask questions from a chat bot, or trigger automations when a run starts or finishes and read test runs, test cases, specs, analytics, and usage downstream.