Execute pytest on specified paths and retrieve a JUnit XML report for test results analysis and CI integration.
MIT
519,862 tools. Updated 2026-09-06 08:15
"Pytest" matching MCP tools:
- Collect pytest tests from given paths without executing them, with an option to include only changed files.MIT
- Run smoke tests before commit or deploy to confirm the project test suite passes. Auto-detects pytest, Jest, Vitest, or Mocha from project config and reports failures, with options to stop at the first error or target a specific suite.MIT
- Generate test skeletons for source code with Jest, pytest, or vitest. Scaffold test stubs for untested public functions so you can begin testing a module without writing boilerplate.MIT
- Run the project's vitest tests in a secure, fixed-argument shell with a 120s timeout and capped output. Restrict by test name or directory path to return pass/fail, exit code, and duration.MIT
- Record each repeated blocker you hit—what you tried, what failed, and minutes lost—so reviewers can cluster and resolve recurring friction.MIT
Matching MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for debugging pytest failures, allowing users to register test failures, apply systematic debugging principles, and analyze failure patterns.261MIT
- FlicenseNot gradedqualityDmaintenanceA Node.js server that integrates with pytest to facilitate the ModelContextProtocol (MCP) service tools, enabling test execution recording and environment tracking.6-
- Extract per-method contract blocks from test files and register them in the UTF registry, enabling contract detail cards in generate_report outputs.MIT
- Create a pending post-incident test from a lesson's attempt/gotcha, preserving provenance and returning the command to arm it as a sensor.Apache 2.0
- Import JUnit XML test execution results into the UTF registry to enable accurate pass/fail reporting.MIT
- Start a shell command as a background task and receive its ID immediately, enabling long-running jobs to continue after the call returns.MIT
- Delegate a coding task to a new DeepSeek Harness subagent with its own runtime process, then verify completion using a shell command. Returns an agent ID immediately or waits for results when desired.MIT
- Execute JavaScript to query Gaffer test and coverage data, analyze project health, debug failures, and identify untested code areas using codemode API functions.MIT
- Lists every memory in a specified project scope, providing the total count and source breakdown. Use to audit the full inventory and verify if specific memories still exist.MIT
- Run 50 lint dimensions across mechanical, shipped, metabolic, and semantic categories to check substrate contract invariants and auto-repair fixable findings during development or release.MIT
- Extract root-cause-analysis for each failed test from the most recent run, including trace steps, screenshots, and video artifacts.MIT
- Launch interactive test recording to transcribe browser actions into runnable test code. Use to build baseline happy-path tests by clicking through complex UI flows.MIT
- Execute test suites under the QA runner and generate structured reports with exit codes, logs, and flaky detection. Supports optional filter to target specific tests across pytest, Jest, Cypress, Go, and Maestro.MIT
- Re-run only the tests that failed in the previous run, supporting pytest, Jest, Cypress, Go, and Maestro. Faster than a full suite, ideal for iterative bug fixes.MIT
- Delegate a scoped coding task to an external AI worker in an isolated git worktree with independent verification.MIT
- Delegate coding tasks to a fresh subagent that runs independently, with a verification command to prove completion. Returns immediately, enabling parallel or asynchronous work.MIT
- Trace call flows, navigate to definitions, find callers/callees, assess impact risk, map test coverage, and uncover co-changing files—all through a single code-intelligence command.MIT