gen-ut

Generate standard unit tests for Apache ShardingSphere target classes.

20.8k|6.9k|Updated Jan 18, 2016
One-click install
npx skills add https://github.com/apache/shardingsphere --skill gen-ut
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gen-ut
Source: https://github.com/apache/shardingsphere/tree/main/.codex/skills/gen-ut
Command: npx skills add https://github.com/apache/shardingsphere --skill gen-ut

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates standardized unit tests for target classes in Apache ShardingSphere to improve coverage and maintainability without manual boilerplate.

Core Features & Use Cases

  • Generates test scaffolding for target classes based on project conventions.
  • Enforces unified testing rules to reach 100% class/line/branch coverage.
  • Supports module-scoped test generation and discovery of related tests to minimize duplication.

Quick Start

Provide the target class list and optional module, then run the unit test generator to produce tests.

Frequently Asked Questions about gen-ut

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate unit tests for Java classes to achieve 100% line and branch coverage?

To generate unit tests for Java classes with 100% coverage, provide a target class list and optional module name. The generator discovers related tests and applies unified rules to produce standard test scaffolding.

How does automated test generation handle existing test duplication in Maven modules?

Automated test generation discovers related tests within Maven modules to minimize duplication. It analyzes existing test structures before generating new scaffolding, ensuring standardized coverage without repeating boilerplate code.

Can I use this unit test generator for Java projects outside of Apache ShardingSphere?

This unit test generator is specifically designed for Apache ShardingSphere target classes. It enforces project-specific unified testing rules and conventions, making it specialized for that ecosystem rather than general Java projects.

What is the best way to enforce strict quality gates for unit test coverage across multiple modules?

To enforce strict quality gates for coverage across modules, apply unified testing rules during generation. The tool targets 100% class, line, and branch coverage, ensuring consistent test standards throughout the project.

Do I need to manually specify test class names when generating unit tests for a target class list?

You do not need to manually specify test class names. You provide a target class list and optional module, and the generator discovers related tests and automatically produces the appropriate test scaffolding.

Why does unit test generation require a target class list instead of scanning the whole project?

Unit test generation requires a target class list to apply unified rules precisely and discover related tests effectively. Scanning the entire project would bypass the module-scoped control needed to reach 100% coverage.