Skip to main content
Configure project identity, API keys, automated reports, AI features, integrations, and branch mapping.

General

Project General settings with name and description fields Owners and Administrators can delete a project. Deletion is immediate, with no restore window (unlike organization deletion, which has a 7-day window). The project name and plan slot are free to reuse right away.
Before deleting, revoke API keys, disconnect webhooks, and export any required reports.

API Keys

API Keys table listing project keys and tokens Create project credentials for local runs and CI. Pick Ingestion for result uploads or Pipeline for Azure DevOps and TeamCity plugins. Expiration options: 30, 60, 90, or 180 days. Revoke or delete a key to invalidate it immediately. Create a replacement, update CI, then delete the old key when a key expires or is exposed. Full create and CI secret steps: Generate API Keys.

Automated Reports

Schedule PDF summaries of test run data and email them to recipients.
  1. Click Create Automated Report
  2. Enter a name, recipients, schedule, and optional tag or environment filters
  3. Create the report, then use Enable/Disable to control whether it runs
Step-by-step content and preview: Automated Reports.

AI Features

AI feature toggles in project settings Enable AI Insights is the master switch. With it on, toggle each feature independently. All features are on by default. Changes apply from the next test run. Existing insights on past runs stay visible. Owner and Administrator only. Disabling AI does not stop streaming, reporting, or non-AI features. See AI Overview.

TestDino Add-ons

Embed live SVG badges in GitHub or GitLab READMEs from Integrations → TestDino Add-ons → Status Badges.
GitHub status badges configuration
Badge types and setup: Status Badges.

Integrations

Connect CI/CD, issue trackers, and Slack from this tab. Install steps and permissions live under Integrations. CI/CD integrations list in project settings For Slack App and GitHub summaries, map branch environments to channels or targets when you use Branch Mapping. If no mapping matches, TestDino uses the default channel.

Branch Mapping

Map repository branches to environments so runs show under the right environment across the product. Branch mapping table with environments and patterns
  1. Enter Name and a short Label
  2. Optionally set a description and color
  3. Add Branch patterns: exact (main) or pattern/regex (^feature/)
  4. Save. Changes can take up to 2 minutes to apply
A branch pattern can belong to only one environment. Duplicate patterns across environments are blocked on save. Pattern details and regex examples: Environment Mapping.

Branch Pinning

Pin branches you check often so they stay at the top of every Branch filter under Filter Customization. Filter Customization table with the Branch row and pinned branch chips
  1. Go to Project Settings → Branch Mapping → Filter Customization
  2. On the Branch row, select Configure
Filter Customization table with the Branch row and its Configure button
  1. Search and select branches to pin, then Save
Pinned branches stay at the top even when you change the environment filter. Patterns cannot be pinned, only real branch names from test runs.

Generate API Keys

Create and store project API keys

Environment Mapping

Branch patterns and regex reference

Integrations

Connect CI, Slack, and issue trackers

AI Overview

How AI features classify and group failures