MCP Test Automation

Created By
syedzubairalam1a year ago
Overview

What is MCP Test Automation?

MCP Test Automation is a project that provides automated testing solutions using Cucumber.js and Playwright, aimed at enhancing the efficiency and reliability of web application testing.

How to use MCP Test Automation?

To use MCP Test Automation, you need to set up the project by installing dependencies and configuring the test settings. You can run the tests using various npm commands based on your requirements.

Key features of MCP Test Automation?

  • Supports multiple browsers: Chromium, Firefox, and WebKit.
  • Configurable test settings through a configuration file and environment variables.
  • Options for headless and headed test execution.
  • Automatic screenshot capture on test failure.
  • Ability to generate HTML reports for test results.

Use cases of MCP Test Automation?

  1. Automating login functionality tests for web applications.
  2. Testing project creation and item management features.
  3. Running tests in different browser environments to ensure compatibility.

FAQ from MCP Test Automation?

  • What browsers are supported?

MCP Test Automation supports Chromium, Firefox, and WebKit.

  • How do I run the tests?

You can run the tests using npm commands like npm run mcp for all tests or specify options for headless mode, specific browsers, or particular test cases.

  • Can I customize the test configuration?

Yes! You can modify the config/test-config.js file or use environment variables to customize the test settings.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
syedzubairalam1
Star
0
Language
HTML
License
-
Tags

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 minutes ago