Generate executable Playwright or API test code from provided test cases and steps, writing output to a specified directory.
MIT
670,897 tools. Updated 2026-10-17 19:56
"Creating Playwright Tests by Exploring a Website and Generating Test Cases" matching MCP tools:
- Converts structured test cases into Playwright automation code. Provide positive, negative, boundary, and edge cases to generate executable JavaScript tests.-
- Generate Playwright test cases for Midscene by providing code examples that help create end-user test scenarios after verifying each step with MCP methods.-
- Get the full list of test cases with latest execution status, including never-run ones as NOT_RUN. Use to answer how many tests you have or list scenarios for an analysis.MIT
- Unlink test cases from a Jira requirement by providing test case keys or filter criteria to clean up traceability links.MIT
- Remove test cases from a QTM4J test cycle by specifying keys, applying filters, or unlinking all at once. Simplifies cycle cleanup before repopulation.MIT
Matching MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that automates Playwright-based UI and API testing, supporting test case generation from requirements or API specs, and execution with detailed reports.8 npm1MIT
- AlicenseAqualityBmaintenanceEnables querying a dataset of Japanese advertising-law enforcement actions, offering search, retrieval, recent listings, and statistical summaries so models can cite real orders rather than inventing them.4MIT
Matching MCP Connectors
DMCA.com cases. Your own token via Authorization: Bearer. No function key, no shared token.
Find psychological self-assessment tests in English, Spanish and Russian, with links to take them.
- Create test cases for Tenzir pipeline operators by defining input/output pairs or generating test scaffolds for later execution.Apache 2.0
- Delete BearQ test cases by ID. Archives them for reversible deletion; rejects protected tests.MITDestructive
- Retrieve test cases linked to a requirement for traceability analysis, or find unlinked test cases to identify coverage gaps and plan testing.MIT
- Link test cases to a Jira requirement using test case keys or filter criteria, enabling traceability between Jira requirements and QTM4J test cases.MIT
- Link test cases to a QTM4J test cycle by key or filter criteria, automatically resolving IDs and versions, with options for assignee, environment, and execution details.MIT
- Retrieve the active test project directory and its .mob test cases to discover the project path and available tests.Apache 2.0
- Add existing test cases to a test collection, skipping duplicates to prevent errors. Only cases from the same project are accepted.MIT
- Retrieve complete test execution results grouped by table with pagination, filter failures, and view summaries after running tests.LGPL 3.0
- Retrieve test cases linked or not linked to a QMetry test suite by its ID to plan execution, analyze coverage, or identify gaps.MIT
- Link test cases to a QMetry test suite using test suite ID and test case version IDs. Optionally link test cases from requirements to automate suite composition.MIT
- Organize test cases by creating a test set with a name and optional parameters, enabling structured evaluation scenarios.MIT
- Convert test cases from a completed generation job into runnable Playwright, Cypress, Selenium, or Puppeteer scripts using a source job ID.MIT
- Link requirements-linked test cases to a QMetry test suite by providing test suite ID and test case version IDs. Automates bulk test suite composition by assigning requirement-derived test cases.MIT
- Retrieve concise test execution summaries with key statistics—execution time, total tests, passed, and failed—for a project. Get a high-level view of results without examining individual test cases.LGPL 3.0
- Analyze bug reports to generate durable regression tests and prevent recurrence. Returns root cause, affected areas, and test cases with reproduction steps.MIT