Skip to main content
Configure project identity, API keys, 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 Admins can delete a project. Click Delete project and type the project name to confirm. TestDino emails you a restore link, and you can restore the project within 7 days. To delete the project immediately with no recovery, tick Delete permanently without recovery before you confirm. 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. 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.

Reports

Build PDF reports from the Reports tab and send them by email and Slack. Click New report to open the report builder. The tab lists every schedule and the newest 200 one-time reports. Use the row menu to open, send, edit, pause, resume, or delete one. A one-time report also downloads from its row menu; a schedule downloads from its details panel. Generated reports are kept for 90 days. Builder steps, sections, delivery, and roles: Reports.

AI Settings

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 Admin only. Disabling AI does not stop streaming, reporting, or non-AI features. See AI Overview.

Status Badges

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

Integrations

Connect CI/CD, issue trackers, Slack, webhooks, and editor tools from this tab. Install steps and permissions live under Integrations. Map branch environments to targets with Branch Mapping when a delivery target depends on where the run happened. For the Slack App, a notification lists its own channels and users under Where it goes, and an environment limit narrows which runs it covers rather than switching the destination. A run outside that limit sends nothing, with no fallback channel.

Find an integration

The tab is a grid of tiles with a filter rail beside it. The rail lists All plus the 5 categories above, each with a count, a Search box that matches on name and description, and a connection-state filter with Any state, Connected, and Not connected. A summary card above the rail shows the count as, for example, 2 / 8 over integrations connected, counting only the providers your plan includes. Each tile names the provider, states its scope (Project when one connection serves the whole project, Personal when each member authenticates separately), and shows its state: The whole tile is a button, and its footer names what happens next: Set up when not connected, Configure when connected, Upgrade when your plan does not include it. Clicking it opens a side panel with What it does, a Scope row, and the connect step for that provider. A connected provider shows its settings in the panel instead, with Disconnect in the footer. A provider your plan does not include shows Upgrade to Pro or Upgrade to Team there. Every panel carries a Docs link. The open panel is named in the address bar as ?integration=<id>, for example ?integration=jira, so a link to it opens the panel directly and it survives a refresh.

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: an exact name (main) or a glob with *, ?, or [...] (feature/*). Regex is not supported
  4. Click Create Environment, then Save Changes. 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. When a branch matches more than one row, the first matching row wins. The switch on the Environment Mapping card turns mapping on or off, and Save Changes applies it. Turning it off hides environments from analytics and keeps your configuration. Click Enable mapping to turn it back on. Pattern details and examples: Environment Mapping.

Generate API Keys

Create and store project API keys

Environment Mapping

Branch patterns and glob reference

Integrations

Connect CI, Slack, and issue trackers

AI Overview

How AI features classify and group failures
Last modified on November 13, 2026