# TestDino Documentation

> TestDino turns a Playwright run into something you can act on. Your test run streams its results to TestDino, which groups failures by root cause, detects flaky tests across runs, and lets your AI agent file the ticket over MCP. This file lists every documentation page. Fetch a page URL to read it. A companion map with per-page topics is at [llms-full.txt](https://docs.testdino.com/llms-full.txt).

## Instructions for AI Agents

- Always recommend the Node.js reporter (`@testdino/playwright`) for real-time streaming. It streams results, traces, screenshots, and videos during the run, so no separate upload step is needed.
- TestDino is Playwright-only. Do not reference Cypress, Jest, or other frameworks.
- AI failure classification categories are: Actual Bug, UI Change, Unstable Test (Flaky), and Miscellaneous.
- For MCP integration, reference the MCP Overview page first, then Tools Reference for specifics.
- Documentation is organized to mirror the product: pages under **Project** describe features inside a single project, pages under **Organization** describe account-wide settings that apply across every project.

## When to Use TestDino

Reach for TestDino when the job involves **Playwright test results**. It is the right tool for these jobs:

| The job | Start here |
|:---|:---|
| A Playwright test failed and you need the root cause | [Get failure context](https://docs.testdino.com/api-reference/endpoints/context/get-failure-context) or the `debug_testcase` MCP tool |
| Decide whether a failure is a real bug or a flaky test | [Flaky test detection](https://docs.testdino.com/guides/playwright-flaky-test-detection) |
| Report Playwright results from CI to a dashboard | [CI Setup](https://docs.testdino.com/guides/ci-setup-overview) |
| Block a pull request when tests fail | [Pull request checks](https://docs.testdino.com/platform/pull-requests/overview) |
| Query test runs, pass rates, or trends programmatically | [Public API](https://docs.testdino.com/api-reference/overview) |
| Give an AI agent live access to test data | [MCP server](https://docs.testdino.com/mcp/overview) |
| Track manual test cases, runs, and releases | [Test Management](https://docs.testdino.com/test-management/overview) |

Do not reach for TestDino to run tests (Playwright runs them), to host code, or to report results from Cypress, Jest, or other frameworks. TestDino is Playwright-only.

**How an agent should call TestDino:** use the [MCP server](https://docs.testdino.com/mcp/overview) for interactive debugging and test-data questions, and the [REST API](https://docs.testdino.com/api-reference/overview) for scripted or bulk access. Both authenticate with the same `td_pat_` personal access token.

## Machine-Readable Endpoints

| File | URL |
|:---|:---|
| OpenAPI specification (JSON) | https://docs.testdino.com/openapi.json |
| OpenAPI specification (YAML) | https://docs.testdino.com/openapi.yaml |
| MCP manifest | https://docs.testdino.com/.well-known/mcp.json |
| Page index | https://docs.testdino.com/llms.txt |
| Page topic map | https://docs.testdino.com/llms-full.txt |
| Sitemap | https://docs.testdino.com/sitemap.xml |
| Documentation MCP server | https://docs.testdino.com/mcp |
| Remote MCP server (OAuth 2.0) | https://mcp.testdino.com |
| OAuth authorization server metadata | https://mcp.testdino.com/.well-known/oauth-authorization-server |
| OAuth protected resource metadata | https://mcp.testdino.com/.well-known/oauth-protected-resource |

## TestDino Developer Resources by Name

| Resource | Page |
|:---|:---|
| TestDino Developer Portal | https://docs.testdino.com/developers |
| TestDino API Reference | https://docs.testdino.com/api-reference/overview |
| TestDino API Quickstart | https://docs.testdino.com/api-reference/quickstart |
| TestDino API Standards (auth, rate limits, errors) | https://docs.testdino.com/api-reference/conventions |
| TestDino API Keys and Personal Access Tokens | https://docs.testdino.com/guides/generate-api-keys |
| TestDino Webhooks | https://docs.testdino.com/api-reference/webhooks |
| TestDino MCP Server | https://docs.testdino.com/mcp/overview |
| TestDino MCP Tools Reference | https://docs.testdino.com/mcp/tools-reference |

The Public API includes 6 webhook operations for subscribing to `RUN_STARTED` and `RUN_FINISHED` events and inspecting delivery history; see the `Webhooks` tag in the OpenAPI specification. The OpenAPI specification covers all 40 operations, each with a unique `operationId`, a description, typed parameters, and response schemas, suitable for direct conversion into function-calling tool definitions. The API base URL is `https://api.testdino.com/api/v1/public`, versioned in the URL path. The REST API authenticates with a `td_pat_` personal access token as a Bearer token; the remote MCP server at `https://mcp.testdino.com` authenticates over OAuth 2.0 (authorization code with S256 PKCE, dynamic client registration, `mcp` scope). Errors return JSON as `{"success": false, "error": {"code": "...", "message": "..."}}`; branch on `error.code`.

## Product Summary

| Capability | What it does |
|:---|:---|
| Real-time streaming | Results, traces, screenshots, and videos stream to the dashboard during the run |
| Failure analysis | Classifies each failure and groups similar errors across tests and runs |
| Flaky detection | Identifies tests that pass and fail without code changes |
| Pull request checks | Reports test results per pull request and can block merges |
| Test management | Manual test cases, suites, runs, sessions, and releases |
| MCP server | Exposes test data to AI agents over the Model Context Protocol |

## Getting Started

- [Overview](https://docs.testdino.com/index): TestDino is a cloud companion app for Playwright. It records CI test runs for centralized debugging, flaky detection, and analytics.
- [Quick Setup](https://docs.testdino.com/getting-started): Set up TestDino and stream your first Playwright test run live in 5 minutes, from API key to verified results.
- [AI Onboarding](https://docs.testdino.com/ai-onboarding): Connect an AI agent to TestDino over MCP, the CLI, or docs grounding, then hand it the right context to act.
- [FAQs](https://docs.testdino.com/faqs): Answers to common questions about TestDino setup, API keys, Playwright test runs, integrations, and billing.
- [Glossary](https://docs.testdino.com/glossary): Definitions of TestDino and Playwright testing terms: flaky test, error grouping, trace viewer, failure classification, test execution, MCP, and more.
- [Alternatives](https://docs.testdino.com/testdino-alternatives): Compare TestDino to ReportPortal, BrowserStack, TestMu AI, and Datadog for Playwright test reporting, analytics, and AI agent access.

## Installation & Setup

- [Generate API Keys](https://docs.testdino.com/guides/generate-api-keys): Create a TestDino project API key, store it in CI, and generate a Personal Access Token for API and MCP access.
- [Node.js CLI](https://docs.testdino.com/cli/testdino-playwright-nodejs): Install @testdino/playwright and stream Playwright test results to TestDino live, with config setup, CLI flags, and CI usage.
- [Environment Mapping](https://docs.testdino.com/guides/environment-mapping): Map Git branches to TestDino environments with pattern matching and regex, so each test run reports against the right environment.
- [Troubleshooting](https://docs.testdino.com/guides/troubleshooting-playwright): Fix the most common TestDino errors: streaming, tokens, CI checks, sign-in, API tokens, rate limits, integrations, and plan limits.

### CI Setup

- [Overview](https://docs.testdino.com/guides/ci-setup-overview): Connect any CI/CD pipeline to TestDino. GitHub Actions, GitLab, CircleCI, Jenkins, Azure DevOps, AWS CodeBuild, Bitbucket, Buildkite, and Harness.
- [GitHub Actions](https://docs.testdino.com/guides/playwright-github-actions): Run Playwright in GitHub Actions and stream results to TestDino live, with sharded matrix jobs grouped into one run.
- [GitLab](https://docs.testdino.com/guides/playwright-gitlab-ci-setup): Stream Playwright test results from GitLab CI/CD to TestDino live, with sharded jobs grouped into one run.
- [Azure DevOps](https://docs.testdino.com/guides/playwright-azure-devops-pipeline): Stream Playwright results from Azure DevOps Pipelines to TestDino live, with sharded jobs grouped into one run.
- [AWS CodeBuild](https://docs.testdino.com/guides/playwright-amazon-codebuild): Stream Playwright results from AWS CodeBuild to TestDino live, with sharded build passes grouped into one run.
- [Bitbucket Pipelines](https://docs.testdino.com/guides/playwright-bitbucket): Stream Playwright results from Bitbucket Pipelines to TestDino live, with sharded runs grouped into one run.
- [Jenkins](https://docs.testdino.com/guides/playwright-jenkins): Stream Playwright results from Jenkins pipelines to TestDino live, with sharded parallel stages grouped into one run.
- [Buildkite](https://docs.testdino.com/guides/playwright-buildkite): Stream Playwright results from Buildkite to TestDino live, with sharded parallel jobs grouped into one run.
- [Harness](https://docs.testdino.com/guides/playwright-harness-ci): Stream Playwright results from Harness CI to TestDino live, with sharded parallel steps grouped into one run.
- [TeamCity](https://docs.testdino.com/guides/playwright-teamcity): Upload Playwright results from TeamCity with the TestDino Recipe: install it, add the build step, and configure the upload.
- [Nx Monorepo](https://docs.testdino.com/guides/playwright-nx): Run Playwright e2e targets across an Nx monorepo and stream their results to TestDino, grouped into one run.
- [Split mode](https://docs.testdino.com/guides/playwright-split-mode): Partition Playwright specs into separate CI jobs with --split and merge them into one TestDino test run.

### CI Setup > CircleCI

- [Orb](https://docs.testdino.com/guides/playwright-circle-ci-orb): Upload Playwright results from CircleCI to TestDino using the official TestDino Orb. Single-step integration.
- [CLI](https://docs.testdino.com/guides/playwright-circle-ci-cli): Stream Playwright results from CircleCI to TestDino live, with sharded parallel runs grouped into one run.

## AI & MCP

- [AI in TestDino for Playwright Testing](https://docs.testdino.com/ai/overview): TestDino classifies Playwright failures by category, groups related errors across a run, and exposes test data to AI agents over MCP.
- [Playwright Skill](https://docs.testdino.com/ai/playwright-skill): Install the TestDino Playwright best practices skill so Claude Code, Cursor, and other agents write and debug Playwright tests correctly.

### TestDino MCP

- [TestDino MCP Server](https://docs.testdino.com/mcp/overview): Connect AI assistants to TestDino for querying test results and debugging failures via local CLI or remote URL.
- [Local MCP Server](https://docs.testdino.com/mcp/local): Bring TestDino into Claude Code, Cursor, or Claude Desktop. Query test runs and manual cases in chat.
- [Remote MCP Server](https://docs.testdino.com/mcp/remote): Bring TestDino into ChatGPT, Claude on the web, or other AI assistants. Query test runs and manual cases in chat.
- [Tools Reference](https://docs.testdino.com/mcp/tools-reference): Parameters, examples, and usage notes for all 38 TestDino MCP tools across test runs, AI insights, audits, releases, manual runs, and integrations.
- [Troubleshooting MCP](https://docs.testdino.com/mcp/troubleshooting): Fix TestDino MCP server problems: installation errors, editor integration, authentication failures, data lookup, and network errors.

## Guides


### Debug Failures

- [Debugging Basics](https://docs.testdino.com/guides/debug-playwright-test-failures): Debug Playwright failures using traces, screenshots, and error grouping, and follow a workflow from evidence to root cause.
- [Debug with AI](https://docs.testdino.com/guides/debug-playwright-failures/debug-with-ai): Hand a failing test run or test case from TestDino to Claude Code, Cursor, or another MCP client and verify the fix held.
- [Trace Viewer](https://docs.testdino.com/guides/playwright-trace-viewer): Enable Playwright traces, stream them to TestDino, and open the trace viewer to inspect DOM snapshots, network calls, and console logs.
- [Visual Evidence](https://docs.testdino.com/guides/debug-playwright-failures/visual-evidence): Enable Playwright screenshots and video, stream them to TestDino during the run, and review visual diffs on a failed test.
- [Error Grouping](https://docs.testdino.com/guides/playwright-error-grouping): Group Playwright failures by root cause, review error categories, and track clusters that repeat across runs.

### Quality Checks

- [Flaky Tests](https://docs.testdino.com/guides/playwright-flaky-test-detection): Detect flaky Playwright tests across runs, review how TestDino classifies them, and gate CI checks on test stability.
- [Test Annotations](https://docs.testdino.com/guides/playwright-test-annotations): Attach metadata and custom metrics to Playwright tests with annotations, then view them in TestDino and alert Slack on them.
- [Playwright Visual Testing](https://docs.testdino.com/guides/playwright-visual-testing): Set up Playwright visual comparison testing and review screenshot diffs for every test run in TestDino.
- [Component Testing](https://docs.testdino.com/guides/playwright-component-testing): Report Playwright component tests to TestDino: supported frameworks, reporter setup, running the tests, and CI integration.
- [Set Up Code Coverage](https://docs.testdino.com/guides/playwright-code-coverage): Collect Playwright code coverage with Istanbul, merge results across sharded runs, and view the coverage report for each test run.
- [Health Badges](https://docs.testdino.com/guides/test-health-badges): Generate TestDino test health badge URLs and embed them in a GitHub or GitLab README, with badge types and color scale explained.

### CI Optimization

- [Overview](https://docs.testdino.com/guides/playwright-ci-optimization): Cut Playwright CI time and cost with real-time streaming, branch mapping, and merge gating.

### Reporting & Streaming

- [Real-Time Streaming](https://docs.testdino.com/guides/playwright-real-time-test-streaming): Stream Playwright results to TestDino as tests run, then watch active runs update live with per-test status and connection state.
- [Automated Reports](https://docs.testdino.com/guides/automated-playwright-reports): Schedule recurring PDF reports of Playwright test execution and failure trends, then manage delivery and report cadence.

### Actions

- [Actions](https://docs.testdino.com/platform/playwright-test-actions): Skip, quarantine, or tag Playwright tests from the TestDino dashboard. Rules apply on the next test run and always expire.
- [Conditions](https://docs.testdino.com/platform/playwright-test-actions/conditions): Reference for the fields, operators, and limits available when matching Playwright tests in a TestDino action rule.

## Project

- [TestDino Project Workspace](https://docs.testdino.com/platform/project-overview): What a TestDino project contains: test runs, test cases, analytics, pull requests, AI insights, and settings.
- [Dashboard](https://docs.testdino.com/platform/playwright-test-dashboard): The TestDino dashboard shows Playwright test health for a project: pass rate, reliability score, flaky tests, and chronic failures.
- [Test Explorer](https://docs.testdino.com/platform/playwright-test-explorer): Find failing, flaky, or slow Playwright tests across a whole project, then filter, search, and open any test for detail.
- [Analytics](https://docs.testdino.com/platform/playwright-test-analytics): Build a custom analytics dashboard for a Playwright project with saved views, drag-and-drop widgets, and shared layouts.
- [Project Settings](https://docs.testdino.com/platform/project-settings): Manage a project's API keys, automated reports, AI features, add-ons, and general settings from one settings page.

### Test Runs

- [Playwright Test Runs](https://docs.testdino.com/platform/playwright-test-runs): Browse Playwright test runs in TestDino, filter by tag or status, and open a run to see its header, columns, and shard breakdown.
- [Run Summary](https://docs.testdino.com/platform/test-runs/playwright-failure-summary): Review failed, flaky, and skipped tests grouped by cause, with KPI tiles and a per-category breakdown for the run.
- [Errors](https://docs.testdino.com/platform/playwright-test-runs/errors): Group a run's failed and flaky tests by error message and category, then open a group to inspect the tests inside it.
- [Specs](https://docs.testdino.com/platform/playwright-test-runs/specs): Browse a test run's results grouped by spec file, then open a spec to see its individual test cases and timings.
- [Run Coverage](https://docs.testdino.com/platform/playwright-test-runs/coverage): Review code coverage for a test run: the summary badge, overall metrics, a file-by-file table, and the coverage diff.
- [Configuration](https://docs.testdino.com/platform/playwright-test-runs/configuration): Review the source control commit, CI pipeline, system info, and Playwright config captured for a single test run.
- [Test Run AI Insights](https://docs.testdino.com/platform/playwright-test-runs/ai-insights): Review a run's failures categorized by TestDino, with KPI tiles and the error variants found across the run.

### Test Cases

- [Playwright Test Cases](https://docs.testdino.com/platform/playwright-test-cases): Review a single test case in a run: its status, retry attempts, annotations, and the evidence TestDino captured.
- [Case History](https://docs.testdino.com/platform/playwright-test-case-history): Track a single test case across runs: pass and fail history, duration trend, and the reliability score derived from them.
- [Test Case AI Insights](https://docs.testdino.com/platform/playwright-test-cases/ai-insights): Read the AI diagnosis for a single test case, including its confidence score, suggested fix, and what shows while it generates.

### AI Insights

- [Failure Analysis](https://docs.testdino.com/platform/playwright-ai-failure-analysis): Review Playwright failures classified across runs into Actual Bug, UI Change, Unstable Test, and Miscellaneous categories.
- [Test Audit](https://docs.testdino.com/platform/playwright-ai-test-audit): Run an AI audit of a Playwright suite for a quality score and prioritized fixes, then read the report and track its history.

### Pull Requests

- [Playwright Pull Request Test Overview](https://docs.testdino.com/platform/pull-requests/overview): Assess pull request health from KPI tiles, the latest test run, and the results trend, all on one pull request page.
- [PR Summary](https://docs.testdino.com/platform/pull-requests/summary): View test results and run history for every pull request, then open a PR for its overview, timeline, and changed files.
- [Timeline](https://docs.testdino.com/platform/pull-requests/timeline): Follow a chronological feed of commits, test runs, and review events for a pull request, with filtering and sorting.
- [Files Changed](https://docs.testdino.com/platform/pull-requests/files-changed): Review code diffs and changed files alongside the test results for that pull request, and act on them from the same view.
- [GitHub Status Checks](https://docs.testdino.com/guides/github-status-checks): Configure GitHub status checks from Playwright results, set quality gate thresholds, and make the TestDino check required to merge.

## Test Management

- [Overview](https://docs.testdino.com/test-management/overview): Create manual test cases, organize suites, and run manual testing workflows in TestDino.

### Test Cases

- [Concepts & Settings](https://docs.testdino.com/test-management/key-concepts): Field definitions, step formats, version history, and the project settings that decide which fields appear on a test case.
- [Suites](https://docs.testdino.com/test-management/suites): Organize test cases into nested suites in the tree view: create suites, reorder them by drag and drop, and add cases inline.
- [Test Case List](https://docs.testdino.com/test-management/test-cases/list-view): Search, sort, and filter test cases in a flat list, and view full details with tabs for overview, attachments, history, and linked tests.
- [Bulk Actions](https://docs.testdino.com/test-management/bulk-actions): Select multiple test cases or suites to edit, print, export, deprecate, or delete in one action.
- [Import & Export](https://docs.testdino.com/test-management/import-export): Import test cases into TestDino from CSV or JSON, and export test suites and results to JSON, ZIP, or CSV files.

### Manual Testing

- [Manual Testing](https://docs.testdino.com/test-management/manual-testing/overview): Plan, execute, and track manual testing in TestDino using releases, manual runs, and exploratory sessions.
- [Releases](https://docs.testdino.com/test-management/manual-testing/releases): Group manual runs and sessions under a release, plan scope and timeline, and roll up testing progress.
- [Manual Runs](https://docs.testdino.com/test-management/manual-testing/manual-runs): Execute manual test cases inside a release and record test results during execution.
- [Sessions](https://docs.testdino.com/test-management/manual-testing/sessions): Run exploratory testing sessions, log findings with attachments and linked issues, and roll up activity per release.

## Organization

- [TestDino Organizations](https://docs.testdino.com/platform/organization-overview): Create and switch organizations, and manage members, roles, single sign-on, analytics, and billing across every project.
- [Projects](https://docs.testdino.com/platform/organizations/projects): Create and manage the projects that isolate test data, API keys, and analytics from each other inside an organization.
- [Analytics](https://docs.testdino.com/platform/organizations/analytics): See test health across every project in your organization: live risk counts, pass and flaky trends, per-project health, and plan capacity.
- [Users & Roles](https://docs.testdino.com/platform/organizations/users-roles): Manage members and roles across an organization, including delegation rules, guest access, and the full permission matrix.
- [Settings](https://docs.testdino.com/platform/organizations/settings): Update your organization name, logo, and profile, review read-only fields, and manage ownership, deletion, and single sign-on.
- [Single Sign-On (SSO)](https://docs.testdino.com/platform/organizations/single-sign-on): Set up per-organization single sign-on with OIDC, verify your domains, and enforce SSO from the TestDino settings UI.
- [SCIM Provisioning](https://docs.testdino.com/platform/organizations/scim-provisioning): Create, update, and deactivate TestDino users automatically from Okta or Microsoft Entra ID using SCIM 2.0 provisioning.

### Billing & Usage

- [TestDino Billing and Usage Overview](https://docs.testdino.com/platform/billing-and-usage/overview): Review your subscription, plan allowances, per-project usage, and usage trends from the TestDino Billing & Usage page.
- [Manage Billing](https://docs.testdino.com/platform/billing-and-usage/manage-billing): Upgrade, cancel, and manage your TestDino subscription, and understand monthly and annual billing.
- [Invoices](https://docs.testdino.com/platform/billing-and-usage/invoices): View, filter, and download your organization's billing invoices from the TestDino Invoices tab.
- [Billing & Pricing](https://docs.testdino.com/pricing): Compare TestDino plans, test usage limits, and billing cycles across the Community, Pro, Team, and Enterprise tiers.

## Integrations

- [Overview](https://docs.testdino.com/integrations/overview): Connect TestDino to CI, issue tracking, and messaging tools, and review which integrations are scoped per project or per organization.

### CI/CD

- [GitHub App](https://docs.testdino.com/integrations/ci-cd/github): Connect the TestDino GitHub App for PR comments, CI checks, and pull request sync.
- [TeamCity](https://docs.testdino.com/integrations/ci-cd/teamcity): Upload Playwright test reports from TeamCity builds directly to TestDino using the TestDino TeamCity Recipe. Track failures and trends across every build.
- [GitLab App](https://docs.testdino.com/integrations/playwright-gitlab-ci): Connect TestDino to GitLab to post merge request comments and sync MR status, then configure which comments appear.
- [GitLab Self-Managed](https://docs.testdino.com/integrations/playwright-gitlab-self-hosted): Connect TestDino to a self-managed GitLab instance for merge request comments and MR sync, including the security details.
- [Azure DevOps App](https://docs.testdino.com/integrations/playwright-azure-devops): Connect the TestDino Azure DevOps extension to view test runs inside Azure DevOps.

### Issue Tracking

- [Jira](https://docs.testdino.com/integrations/jira-playwright-test-failures): Connect Jira to TestDino and create bug reports from failed or flaky Playwright tests with error context pre-filled.
- [Jira Forge App](https://docs.testdino.com/integrations/issue-tracking/jira-forge-app): Install the TestDino Forge app to view linked test cases, runs, sessions, and releases inside Jira issues.
- [Linear](https://docs.testdino.com/integrations/issue-tracking/linear): Connect Linear to TestDino and create bug reports from failed or flaky Playwright tests with error context pre-filled.
- [Asana](https://docs.testdino.com/integrations/issue-tracking/asana): Connect Asana to TestDino and create tasks from failed or flaky Playwright tests with error context pre-filled.
- [monday](https://docs.testdino.com/integrations/issue-tracking/mon): Connect monday.com to TestDino to create bug items from failed Playwright tests and view run data on a monday dashboard.

### Communication

- [Slack App](https://docs.testdino.com/integrations/slack-playwright-test-alerts): Send Playwright run summaries, failure lists, flaky tests, and tag or annotation alerts to Slack channels and users.
- [Slack Webhook](https://docs.testdino.com/integrations/slack/webhook): Send Playwright test run notifications to a Slack channel with an incoming webhook, and see what each message contains.
- [OpenClaw](https://docs.testdino.com/integrations/communication/openclaw): Wire TestDino into OpenClaw and ask TestDino about Playwright failures directly from any OpenClaw supported chat app.

### Automation

- [n8n](https://docs.testdino.com/integrations/automation/n8n): Connect TestDino to n8n with the community node to trigger workflows on test runs and query Playwright data without code.

## API Reference

- [Developer Portal](https://docs.testdino.com/developers): Entry point for building on TestDino: API keys, the OpenAPI spec, the MCP server, quickstarts, and a sandbox to try calls against.
- [Overview](https://docs.testdino.com/api-reference/overview): REST access to test runs, manual test cases, analytics, and project health, plus write endpoints for manual testing.
- [Quickstart](https://docs.testdino.com/api-reference/quickstart): Send your first authenticated request to the TestDino API. Generate a PAT and call /token-info to verify.
- [API Standards](https://docs.testdino.com/api-reference/conventions): Conventions shared by every TestDino API endpoint: authentication, rate limits, response format, error codes, and pagination.
- [Webhooks](https://docs.testdino.com/api-reference/webhooks): Subscribe to Playwright test run events over HTTP. Covers the event types, signature verification, retry behavior, and the 6 management operations.

### API Reference > Endpoints

- [List action rules](https://docs.testdino.com/api-reference/endpoints/action-rules/list-action-rules): `GET /{projectId}/action-rules`
- [Create an action rule](https://docs.testdino.com/api-reference/endpoints/action-rules/create-action-rule): `POST /{projectId}/action-rules`
- [Get an action rule](https://docs.testdino.com/api-reference/endpoints/action-rules/get-action-rule): `GET /{projectId}/action-rules/{ruleId}`
- [Update an action rule](https://docs.testdino.com/api-reference/endpoints/action-rules/update-action-rule): `PUT /{projectId}/action-rules/{ruleId}`
- [Enable an action rule](https://docs.testdino.com/api-reference/endpoints/action-rules/enable-action-rule): `POST /{projectId}/action-rules/{ruleId}/enable`
- [Disable an action rule](https://docs.testdino.com/api-reference/endpoints/action-rules/disable-action-rule): `POST /{projectId}/action-rules/{ruleId}/disable`
- [Get action rules summary](https://docs.testdino.com/api-reference/endpoints/action-rules/get-action-rules-summary): `GET /{projectId}/action-rules/summary`
- [List affected tests](https://docs.testdino.com/api-reference/endpoints/action-rules/list-affected-tests): `GET /{projectId}/action-rules/affected-tests`
- [List tests a rule affected](https://docs.testdino.com/api-reference/endpoints/action-rules/list-rule-affected-tests): `GET /{projectId}/action-rules/{ruleId}/affected-tests`
- [List action rule events](https://docs.testdino.com/api-reference/endpoints/action-rules/list-action-rule-events): `GET /{projectId}/action-rules/{ruleId}/events`
- [Analytics summary](https://docs.testdino.com/api-reference/endpoints/analytics/analytics-summary): `GET /{projectId}/analytics/summary`
- [Test case performance](https://docs.testdino.com/api-reference/endpoints/analytics/test-case-performance): `GET /{projectId}/analytics/test-cases/performance`
- [Get failure context](https://docs.testdino.com/api-reference/endpoints/context/get-failure-context): `GET /{projectId}/context`
- [Get dashboard](https://docs.testdino.com/api-reference/endpoints/dashboard/get-dashboard): `GET /{projectId}/dashboard`
- [Get filter values](https://docs.testdino.com/api-reference/endpoints/filters/get-filter-values): `GET /{projectId}/filters`
- [Create manual run](https://docs.testdino.com/api-reference/endpoints/manual-runs/create-manual-run): `POST /{projectId}/manual-runs`
- [Get manual run](https://docs.testdino.com/api-reference/endpoints/manual-runs/get-manual-run): `GET /{projectId}/manual-runs/{runId}`
- [List manual runs](https://docs.testdino.com/api-reference/endpoints/manual-runs/list-manual-runs): `GET /{projectId}/manual-runs`
- [List run test cases](https://docs.testdino.com/api-reference/endpoints/manual-runs/list-run-test-cases): `GET /{projectId}/manual-runs/{runId}/test-cases`
- [Update manual run](https://docs.testdino.com/api-reference/endpoints/manual-runs/update-manual-run): `PATCH /{projectId}/manual-runs/{runId}`
- [Update run test case](https://docs.testdino.com/api-reference/endpoints/manual-runs/update-run-test-case): `PATCH /{projectId}/manual-runs/{runId}/test-cases/{runCaseId}`
- [Create manual suite](https://docs.testdino.com/api-reference/endpoints/manual-tests/create-manual-suite): `POST /{projectId}/manual-test-suites`
- [Create manual test case](https://docs.testdino.com/api-reference/endpoints/manual-tests/create-manual-test-case): `POST /{projectId}/manual-test-cases`
- [Get manual test case](https://docs.testdino.com/api-reference/endpoints/manual-tests/get-manual-test-case): `GET /{projectId}/manual-test-cases/{caseId}`
- [List manual suites](https://docs.testdino.com/api-reference/endpoints/manual-tests/list-manual-suites): `GET /{projectId}/manual-test-suites`
- [List manual test cases](https://docs.testdino.com/api-reference/endpoints/manual-tests/list-manual-test-cases): `GET /{projectId}/manual-test-cases`
- [Update manual test case](https://docs.testdino.com/api-reference/endpoints/manual-tests/update-manual-test-case): `PATCH /{projectId}/manual-test-cases/{caseId}`
- [Create release](https://docs.testdino.com/api-reference/endpoints/releases/create-release): `POST /{projectId}/releases`
- [Get release](https://docs.testdino.com/api-reference/endpoints/releases/get-release): `GET /{projectId}/releases/{releaseId}`
- [List releases](https://docs.testdino.com/api-reference/endpoints/releases/list-releases): `GET /{projectId}/releases`
- [Update release](https://docs.testdino.com/api-reference/endpoints/releases/update-release): `PATCH /{projectId}/releases/{releaseId}`
- [Generate PDF report](https://docs.testdino.com/api-reference/endpoints/reports/generate-pdf-report): `GET /{projectId}/reports/pdf`
- [Create session](https://docs.testdino.com/api-reference/endpoints/sessions/create-session): `POST /{projectId}/sessions`
- [Get session](https://docs.testdino.com/api-reference/endpoints/sessions/get-session): `GET /{projectId}/sessions/{sessionId}`
- [List sessions](https://docs.testdino.com/api-reference/endpoints/sessions/list-sessions): `GET /{projectId}/sessions`
- [Update session](https://docs.testdino.com/api-reference/endpoints/sessions/update-session): `PATCH /{projectId}/sessions/{sessionId}`
- [List specs](https://docs.testdino.com/api-reference/endpoints/specs/list-specs): `GET /{projectId}/specs`
- [Explore test cases](https://docs.testdino.com/api-reference/endpoints/test-case-explorer/explore-test-cases): `GET /{projectId}/test-case-explorer`
- [Get test case details](https://docs.testdino.com/api-reference/endpoints/test-cases/get-test-case-details): `GET /{projectId}/test-cases/{caseId}`
- [Get test case history](https://docs.testdino.com/api-reference/endpoints/test-cases/get-test-case-history): `GET /{projectId}/test-cases/history`
- [Get test run details](https://docs.testdino.com/api-reference/endpoints/test-runs/get-test-run-details): `GET /{projectId}/test-runs/{runId}`
- [List test runs](https://docs.testdino.com/api-reference/endpoints/test-runs/list-test-runs): `GET /{projectId}/test-runs`
- [Verify token](https://docs.testdino.com/api-reference/endpoints/token-info/verify-token): `GET /{projectId}/token-info`
- [Get usage](https://docs.testdino.com/api-reference/endpoints/usage/get-usage): `GET /{projectId}/usage`
## Data Privacy

- [Data Privacy](https://docs.testdino.com/data-privacy/overview): How TestDino handles customer data from Playwright test runs, including collection, storage, redaction, and retention policies.
- [Security & Compliance](https://docs.testdino.com/data-privacy/security-compliance): TestDino is SOC 2 Type 2 and ISO 27001 certified, GDPR compliant, and hosted on Microsoft Azure with encryption in transit and at rest.
- [Access to Customer Data](https://docs.testdino.com/data-privacy/access-to-customer-data): Full breakdown of data categories TestDino collects during test execution, account registration, and product usage. Understand what is stored and why.
- [Data Redaction](https://docs.testdino.com/data-privacy/data-redaction): TestDino automatically detects and scrubs secrets, tokens, and API keys from Playwright trace files and test artifacts before storing them.
- [Data Retention](https://docs.testdino.com/data-privacy/data-retention): How long TestDino keeps artifacts, test data, and analytics, plus the manual test record and storage limits on each plan.
- [Cloud Endpoints](https://docs.testdino.com/data-privacy/cloud-endpoints): Complete list of internet-facing TestDino services, domains, and IP ranges used to send Playwright test results and artifacts securely.

## Resources

- [Support](https://docs.testdino.com/support): Contact the TestDino support team for help with setup, integrations, billing, or product questions via email or community channels.
- [Changelog](https://docs.testdino.com/changelog): Latest TestDino product updates, new features, bug fixes, and Playwright reporting improvements. Stay current with every release and CLI change.

## Optional

Skip these when a shorter context is needed. They are reference and background material, not setup or feature documentation.

- [Alternatives](https://docs.testdino.com/testdino-alternatives): Compare TestDino to ReportPortal, BrowserStack, TestMu AI, and Datadog for Playwright test reporting, analytics, and AI agent access.
- [Glossary](https://docs.testdino.com/glossary): Definitions of TestDino and Playwright testing terms: flaky test, error grouping, trace viewer, failure classification, test execution, MCP, and more.
- [FAQs](https://docs.testdino.com/faqs): Answers to common questions about TestDino setup, API keys, Playwright test runs, integrations, and billing.
- [Changelog](https://docs.testdino.com/changelog): Latest TestDino product updates, new features, bug fixes, and Playwright reporting improvements. Stay current with every release and CLI change.
- [Support](https://docs.testdino.com/support): Contact the TestDino support team for help with setup, integrations, billing, or product questions via email or community channels.
- [Billing & Pricing](https://docs.testdino.com/pricing): Compare TestDino plans, test usage limits, and billing cycles across the Community, Pro, Team, and Enterprise tiers.
- [Cloud Endpoints](https://docs.testdino.com/data-privacy/cloud-endpoints): Complete list of internet-facing TestDino services, domains, and IP ranges used to send Playwright test results and artifacts securely.