Available Integrations
GitHub App
PR comments, CI checks, PR dashboard sync
GitLab
MR comments, merge request dashboard sync
Azure DevOps
View test runs inside Azure DevOps
Jira
Create issues from failed or flaky tests
Jira Forge App
View linked test cases, runs, and sessions inside Jira issues
Linear
Create issues from failed or flaky tests
Asana
Create tasks from failed or flaky tests
monday
Create items from failed or flaky tests
Slack App
Run summaries + annotation-based failure alerts
Slack Webhook
Custom webhook notifications
OpenClaw Chat Bot
Query TestDino from Slack, Telegram, Discord, WhatsApp
n8n
Trigger workflows on test runs, query data with the community node
Connection Scope
| Scope | How It Works | Integrations |
|---|---|---|
| Project-level | Connected once per project. All team members share the same connection. | GitHub App, GitLab, monday, Azure DevOps, Slack App, Slack Webhook |
| User-level | Each team member authenticates individually. Tickets are created under their own account. | Jira, Linear, Asana |
| Token-based | Connected with a Personal Access Token. The token resolves to its project, so no project ID is entered. | n8n |
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.| Integration | Comments | CI Checks | PR/MR Dashboard Sync |
|---|---|---|---|
| GitHub App | PR + commit comments | Pass/fail quality gates | Full sync: overview, timeline, files changed |
| GitLab | MR + commit comments | Not available | Full sync: overview, timeline, files changed |
| Azure DevOps | Not available | Not available | View test runs via VS Marketplace extension |
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.| Integration | Supported Actions |
|---|---|
| Jira | Create issues in a selected Jira project with prefilled fields |
| Jira Forge App | View test cases, runs, sessions, and releases linked from TestDino inside the Jira issue panel |
| Linear | Create issues in a selected Linear team |
| Asana | Create tasks in a selected Asana project |
| monday | Create items in a selected monday board + dashboard widget to view test runs with status |
Communication
Route test run notifications to Slack so your team stays updated without opening TestDino.| Integration | What It Does |
|---|---|
| Slack App | • Run summaries: posts status, pass rate, duration, author, and branch to configured channels with environment-based routing • Annotation alerts: notifies specific channels or users when tests with testdino:notify-slack annotations fail |
| Slack Webhook | • Sends all notifications to a single channel via incoming webhook URL • No environment routing or annotation alerts |
AI & 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.| Integration | What It Does |
|---|---|
| OpenClaw Chat Bot | • Two-way bot powered by the Local MCP Server • Ask TestDino questions in plain language from Slack, Telegram, Discord, WhatsApp, and other channels OpenClaw supports |
| n8n | • Trigger node: starts a workflow when a test run begins or completes • Action nodes: query test runs, test cases, specs, analytics, and usage, and generate PDF reports • Runs as AI-agent tools inside n8n’s AI Agent node |