TestDino

Created By
6 months ago
TestDino MCP boosts your AI assistant with powerful tools and analysis capabilities. It lets your AI analyze test runs, perform root-cause analysis, and detect failure patterns
Overview

What is TestDino?

TestDino is a powerful tool that enhances AI assistants with capabilities to analyze test runs, perform root-cause analysis, and detect failure patterns in automated testing environments.

How to use TestDino?

To use TestDino, integrate it with your AI tools like Claude and Cursor using the Model Context Protocol (MCP). You can install it via npm and configure it to connect with your Playwright test results.

Key features of TestDino?

  • Analyze failed tests and identify root causes.
  • Access test execution history and trends.
  • Retrieve detailed error logs and debugging information.
  • Upload local test results for analysis.
  • Provide insights on test flakiness and performance.

Use cases of TestDino?

  1. Debugging test failures by analyzing error messages and logs.
  2. Monitoring test health and stability over time.
  3. Generating reports summarizing test run results.
  4. Optimizing tests by identifying slow or flaky tests.
  5. Uploading local test results for centralized tracking.

FAQ from TestDino?

  • Can TestDino integrate with any AI assistant?

Yes! TestDino can connect with various AI tools that support the Model Context Protocol (MCP).

  • Is TestDino free to use?

TestDino offers a free tier, but advanced features may require a subscription.

  • How do I get my TestDino API key?

You can generate an API key from your TestDino account settings under API Keys.

Server Config

{
  "mcpServers": {
    "TestDino": {
      "command": "npx",
      "args": [
        "-y",
        "testdino-mcp"
      ],
      "env": {
        "TESTDINO_API_KEY": "your_testdino_api_key"
      }
    }
  }
}
Project Info
Created At
6 months ago
Updated At
6 months ago
Author Name
-
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

20 hours ago
Gpt Scrambler

2 days ago