generate-tests

Generate test cases from code and API specifications using Arrange-Act-Assert.

Updated Dec 31, 2025
One-click install
npx skills add https://github.com/clover-storm/agentic --skill generate-tests-clover-storm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-tests
Source: https://github.com/clover-storm/agentic/tree/main/.claude/skills/generate-tests
Command: npx skills add https://github.com/clover-storm/agentic --skill generate-tests-clover-storm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automatically generates comprehensive test cases based on implemented code and API specifications, reducing manual testing effort and improving coverage.

Core Features & Use Cases

  • Code-driven Test Generation: Derives test cases from source code and API specs to ensure alignment with the actual implementation.
  • Test Documents & Artifacts: Produces backend and frontend test docs and skeleton test files for quick integration.
  • Use Case: When a new API endpoint is added, generate both backend and frontend tests and corresponding documentation in one pass.

Quick Start

Provide target, api_spec_path, and source_path to the skill input to generate tests automatically.

Frequently Asked Questions about generate-tests

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

FAQPage Schema
How do I automatically generate test cases from API specifications and source code?

Test generation automatically creates test cases by analyzing your API specs and source code to identify test points. Provide your target, API spec path, and source code path to produce backend and frontend tests following the Arrange-Act-Assert pattern in a single pass.

What test artifacts does automated test generation produce?

Test generation produces deterministic test documents and skeleton test files for both backend and frontend targets. These artifacts scaffold your test suite and include corresponding documentation, ready for integration into your codebase.

Can I generate tests for both backend and frontend from the same API specification?

Yes, test generation analyzes API specs to derive test cases for both backend and frontend targets simultaneously. A single run produces aligned test scaffolding and docs for both layers, ensuring comprehensive coverage across your stack.

When should I use code-driven test generation instead of writing tests manually?

Use test generation when adding new API endpoints or implementing features from existing specs. It reduces manual testing effort and improves coverage by deriving tests directly from your implementation and specification, catching gaps manual review might miss.

What happens if my API specification doesn't match my current implementation?

Test generation produces tests aligned with both your API spec and source code. Mismatches between spec and implementation surface as divergent test points, helping you identify and reconcile inconsistencies before they reach production.

Does test generation work with any API specification format?

Test generation accepts API specs as input and analyzes them alongside your source code. The metadata supports API-specs as a keyword; consult the Skill documentation for supported specification formats and schema requirements.