Integrations
Overview

Integrations

Integrations connect TestDino to engineering tools.

  • GitHub CI/CD records runs automatically and posts AI summaries to commits and pull requests.

  • The Slack App sends branch-mapped run summaries to chosen channels, with webhook support.

  • Jira and Linear create issues from failed or flaky tests with context prefilled.

TestDino’s integrations are project-scoped and configurable by environment or branch.

This enables precise routing of comments and alerts, controlled access per project, and consistent links and evidence across the toolchain.

How it helps

  • One source of truth - each Jira/Linear ticket links to the exact run and commit.

  • Prefilled issue body - test details, failure context, recent history, and links.

  • File to the right place - select the Jira project or Linear team once.

  • Automated uploads & comments - GitHub app connects testruns to commits/PRs and can post AI summaries; Control where comments appear through branch Environments.

  • Team updates - The Slack App posts compact run summaries to the channel mapped to each branch environment (Slack webhook is also available).

  • Project-scoped - Each project can be independently connected, synced, or disconnected, with access limited to only what’s necessary. You can also set different permissions and controls for each environment, such as staging or production.

What Summaries Contain

GitHub Comments

  • The AI-generated summary posted to commits and pull requests includes:

  • A summary table with counts for passed, failed, flaky, and skipped tests, along with the pass rate and total duration.

  • A detailed Test Failure Analysis that groups failures by test file and outlines the specific error message or cause.

Slack Messages

The test run summary sent to the configured channel includes:

  • The overall status (passed, failed, flaky, or skipped).

  • Success rate and total counts for each test status.

  • Key run contexts, such as duration, environment, and branch.

  • The author and commit message.

  • A View test run button that links directly to the detailed report in TestDino.

What gets added to bug reports

  • Test name and file, branch, environment, run ID, duration, and attempts.

  • Failure cluster and key error line with the failing step or locator.

  • Short failure history for the selected window.

  • Console excerpts that aid reproduction.

  • Links to the TestDino run, Git commit, and CI job.

Available Integrations