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 Project names accept letters, numbers, spaces, dots, underscores, and hyphens, up to 100 characters. The same rule applies wherever you name a project, including the New Project dialog. Organization names allow a wider set, listed in Organizations. 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. 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.

How the tab is grouped

The tab is a grid of cards grouped by what you can do with each one, not by category. Each heading carries a count. A card names the provider and carries a Project badge when the connection is shared by the whole project, plus a Connected chip once it is live. A card your plan does not include shows Upgrade to Pro or Upgrade to Team in place of Connect.

Integration plan requirements

Each provider has its own minimum plan, so a plan can include one issue tracker and not another. Plan comparison and pricing: Billing & Usage.

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.

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