Settings

Project Settings

Central place to configure a project: identity, usage limits, API key management, third-party integrations, and environment-to-branch mapping.

Update project metadata, track monthly execution quota, issue and rotate API keys, connect Jira/Linear/Slack, and map branches to environments.

General

Basic settings

Define the project identity and context shown across the product.

  • Project ID. Read-only identifier used by our platform or support.

  • Project Name. Display name in headers and menus.

  • Description. Short note to describe scope or ownership.

Usage & Quota

usage & quota

Monitor monthly test case execution allowance and billing period.

  • View monthly test case executions used and remaining. The counter resets on the Next reset date.

  • Free Tier includes 1,000 executions per month during beta.

  • Need more capacity? Upgrade to a Paid Tier. If you have unique needs or questions, contact us at support@testdino.com for personalized support.

  • If numbers look stale after a run, click Sync to refetch new data.

API Keys

api keys

Create and manage credentials for local or CI pipelines and tools that send data to TestDino.

Create a Key

  1. Select Generate Key.

  2. Enter a Key Name and Expiration (days), 1 to 365.

  3. Create the key and store the secret in your secret manager.

Manage Keys

  • Copy or view details. Use row actions to retrieve metadata as allowed.

  • Rotate. Create a replacement key, update CI, then revoke the old key.

  • Revoke or delete. Immediately invalidates the key.

Tips

  • Prefer short expirations for CI.

  • Rotate if exposure is suspected.

Integrations

integrations

Manage connections to external systems. For installation, permissions, and workflows, see Integrations.

Quick Links

Typical Actions

  • Connect or disconnect a tool.

  • Provide the required fields, for example, Slack Webhook URL, then Connect.

  • Set default project, team, or channel as prompted.

  • Status shows Inactive or Not connected until configured.

Branch Mapping

It connects branches to environments like production or staging, using exact names or patterns, so your results show up in the right place across the platform.

Mapping uses either exact branch names or wildcard patterns to group many branches under one environment.

branch mapping

Why Does It Matter?

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.

Add or Edit an Environment

  1. Enter Name and a short Label used in chips and filters.
  2. Optionally set a Description and color.
  3. Define Branch patterns:
    • Exact match to bind a single branch, for example, main.
    • Pattern match to bind many branches, for example, feature/*, release/*, hotfix/*.
  4. Save. Changes can take up to 2 minutes to apply.

Notes

  • Environments and branches: a development or staging environment usually covers many branches, for example, feature/123 or user/td-123. Production usually maps to one protected branch, for example, main or master. Teams that run tests on pull request open or merge will execute on the PR’s head branch. Mapping ensures those runs are attributed to the correct environment.
  • Keep labels short, for example, PROD, STAGE, DEV.
  • Review patterns when you add long-lived branches.
  • Limit: up to 10 environments per project.

Danger Zone

Project Deletion

Before requesting deletion, revoke API keys, disconnect webhooks, and export any required reports.
PermissionsOverview