๐ ๐ - Unit test generation, coverage analysis, test planning, fixture generation, and mutation testingโฆ
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP ๆๅก. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-10-14๏ผlast seen 2026-10-16ใThere is no official certification or quality rating here โ we record sources and dates only.
@rog0x/mcp-testing-tools
ไปฅไธๆๅฝ่ช่ฏฅไปๅบ็ README๏ผ็ๆฎต๏ผ ยท ๅจ GitHub ่ฏปๅฎๆด README โ
Testing and quality assurance tools for AI agents, exposed via the Model Context Protocol (MCP).
Tools
generate_tests
Generate test cases from a function signature. Produces four categories of tests as ready-to-run Jest or Vitest code:
- **Happy path** -- valid inputs, expected outputs
- **Edge cases** -- empty strings, zero values, null parameters
- **Error cases** -- missing arguments, wrong types
- **Boundary values** -- extreme numbers, large arrays, NaN
**Parameters:**
| Name | Type | Required | Description |
|------|------|----------|-------------|
| signature | string | Yes | Function signature, e.g. async function fetchUser(id: number): Promise |
| framework | string | No | jest or vitest (default: vitest) |
| module_path | string | No | Import path for the module under test (default: ./module) |
generate_mock_data
Generate realistic mock data for testing. Supported types:
name, email, address, date, uuid, phone, company, credit_card, ip
**Parameters:**
| Name | Type | Required | Description |
|------|------|----------|-------------|
| type | string | Yes | Data type to generate |
| count | number | No | Number of items (default: 10, max: 1000) |
| locale | string | No | en or es (default: en) |
| types | string[] | No | Generate mixed records with multiple field types |
generate_api_mock
Generate mock API responses from a schema definition. Creates realistic JSON payloads for REST endpoints by inferring values from field names and types.
**Parameters:**
| Name | Type | Required | Description |
|------|------|----------|-------------|
| endpoint | string | Yes | API endpoint path |
| method | string | No | HTTP method (default: GET) |
| fields | object[] | Yes | Field schemas with name, type, optional items, fields, nullable, enum |
| count | number | No | Number of records (default: 1, max: 100) |
| status_code | number | No | HTTP status code (default: 200) |
| wrap_in_envelope | boolean | No | Wrap in { success, data, meta } (default: true) |
analyze_test_coverage
Analyze source code and test code to find untested functions. Prioritizes suggestions by:
- Export status (public API surface)
- Cyclomatic complexity estimate
- Parameter count
- Async functions (more error paths)
**Parameters:**
| Name | Type | Required | Description |
|------|------|----------|-------------|
| source_code | string | Yes | Source code to analyze |
| test_code | string | Yes | Existing test code |
| source_file_name | string | No | Filename label (default: source.ts) |