The Enable AI Insights toggle controls all AI features at once. Disable it to turn off every AI feature for the project. Enable it to restore individual feature settings.
NoteDisabling an AI feature does not affect other platform functionality. Test execution, reporting, and all non-AI features continue to work normally.
Embed live SVG badges in GitHub or GitLab READMEs that display test health, flakiness, and test counts from the latest completed run. Configure badges from Integrations → TestDino Add-ons → Status Badges.
GitHub
GitLab
For badge types, color scales, and setup steps, see the Status Badges guide.
GitHub - Test-run summaries on commits and PRs.GitLab - Test-run summaries on merge requests and commits. Only one Git provider (GitHub or GitLab) can be active per project.TeamCity - Upload Playwright test reports from your TeamCity builds directly to TestDino.
Slack Webhook - posts a test run summary to the Slack channel.
Slack App - posts a test run summary to the Slack channel mapped to the run’s branch environment.
NoteIf no environment mapping matches, TestDino posts the summary to the default Slack channel. Map each branch pattern to an environment and select a Slack channel for that environment; environment mapping takes precedence over the default channel. This applies to GitHub as well.
It maps repository branches to specific environments (production, staging, etc.) using exact names or patterns, ensuring your results display in the correct environment throughout the platform.
End-to-end tests often run on pull requests and short-lived branches. Without mapping, those runs fragment across dozens of branch names.Mapping rolls them up to the right environment, so pass rates, volumes, and alerts reflect reality.
Enter Name and a short Label used in chips and filters.
Optionally set a Description and color.
Define Branch patterns:
Exact match to bind a single branch, for example, main.
Pattern match to bind many branches, for example, feature/*, release/*, hotfix/*.
Save. Changes can take up to 2 minutes to apply.
Warning
Environments and branches: A development or staging environment typically encompasses multiple branches, for example, feature/123 or user/td-123. Production typically maps to one protected branch, such as, main or master. Teams that run tests on PRs opened or merged will execute on the PR’s head branch. Mapping ensures those runs are attributed to the correct environment.
When enabled, the --environment flag in your upload command takes priority over branch mapping rules. If you specify --environment=staging, that run goes to staging regardless of which branch triggered it.This is useful when:
You run tests against multiple environments (prod, stage) from a single commit
Your CI pipeline targets specific environments that don’t match your branch naming
You need manual control over the environment assignment for certain runs
Maximum 10 environments per project. If you’ve hit the limit, the CLI run still succeeds but uses branch mapping instead. You’ll see a warning in the CLI output.
Environment names must be valid. Invalid characters cause the upload to fail.
CLI-created runs: When you update branch mapping rules, test runs created via the --environment flag keep their original environment. The CLI value is preserved.
Branch-mapped runs: Existing runs created through branch mapping update to reflect the new rules.
Define the project identity and context shown across the product.
Create and manage credentials for local or CI pipelines and tools that send data to TestDino.
Control which AI-powered features are active for this project. All AI features are enabled by default for new and existing projects.
GitHub - Test-run summaries on commits and PRs.
GitLab - Test-run summaries on merge requests and commits. Only one Git provider (GitHub or GitLab) can be active per project.
TeamCity - Upload Playwright test reports from your TeamCity builds directly to TestDino.
To create issues from failed or flaky tests, use:
