Unit Test Generator

Name: Unit Test Generator
Author: hanqizheng

@hanqizheng

代码仓库

关于 Unit Test Generator

暂无概览

基本信息

分类

开发工具

运行时

node

传输方式

stdio

发布者

hanqizheng

配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "unit-test-generator": {
      "command": "node",
      "args": [
        "YOUR_MCP_SERVER_BUILD_INDEX_PATH"
      ],
      "env": {
        "PROJECT_PATH": "YOUR_COMPONENT_LIBRARY_PROJECT_PATH"
      },
      "transport": "stdio",
      "enabled": true,
      "description": "component library unit test generator"
    }
  }
}

工具

未检测到工具

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is Unit Test Generator?

Unit Test Generator is an MCP server that uses the Model Context Protocol to automatically generate unit tests for component libraries. It is designed for developers working with component-based projects and integrates with Cursor via a local MCP server configuration.

How to use Unit Test Generator?

Clone the repository, install dependencies with npm install, and build with npm run build. Then add it as a global MCP server in Cursor by providing a JSON configuration that specifies the command (node), the path to the built index file, the PROJECT_PATH environment variable pointing to your component library, and the transport type (stdio).

Key features of Unit Test Generator

Generates unit tests for component libraries
Integrates with Cursor via MCP protocol
Uses stdio transport for local execution
Requires only Node.js and npm

Use cases of Unit Test Generator

Automatically create unit tests for a React component library
Maintain test coverage for a growing UI component set
Speed up test writing in a Cursor development workflow

FAQ from Unit Test Generator

What are the dependencies or runtime requirements?

You need Node.js and npm installed. The server is built with npm and run with the node command.

How is the server configured for Cursor?

You add it as a global MCP server in Cursor Settings, providing a JSON block that includes the command, args build index path), environment variable PROJECT_PATH, transport stdio, and enabled flag.

Where does the user data (project files) reside?

The server accesses the component library specified in the PROJECT_PATH environment variable. No external data is transferred; the server runs locally.