test-coverage

Name: test-coverage
Availability: InStock
Author: salesteamtoolbox

Generate convention-compliant unit tests for Python modules with deterministic mocks.

Updated Aug 27, 2026

Search Tags:#code quality #unit testing #pytest #coverage #generate #tests #async mocking

Ready to run

npx skills add https://github.com/SalesTeamToolbox/frood --skill test-coverage-salesteamtoolbox

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-coverage
Source: https://github.com/SalesTeamToolbox/frood/tree/main/.claude/skills/test-coverage
Command: npx skills add https://github.com/SalesTeamToolbox/frood --skill test-coverage-salesteamtoolbox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the guesswork and time sink of writing thorough, convention-following unit tests by turning an existing module into a complete test file automatically.

Core Features & Use Cases

Conventions-aware test generation: Creates tests/test_<module_basename>.py following Frood’s naming and structure patterns.
Context-driven implementation: Reads the target module and tests/conftest.py to align with available fixtures and expected testing approach.
Idempotent safety: Detects an existing tests/test_<module_basename>.py and stops to avoid overwriting developer work.
Good coverage defaults: Produces tests that target happy paths, edge cases, and error handling, including async methods via pytest.mark.asyncio.

Quick Start

Ask the skill to generate tests for your module by running: /test-coverage core/sandbox

Frequently Asked Questions about test-coverage

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

FAQPage Schema

How do I generate unit tests for an existing Python module automatically?▼

To generate unit tests automatically, this skill resolves your module's source path, reads existing test fixtures, and produces a convention-compliant test file targeting happy paths, edge cases, and error handling.

Does this test generator work with async Python code paths?▼

Yes, the generated tests support async code paths by utilizing pytest.mark.asyncio, ensuring that asynchronous methods are properly covered with deterministic mocks and clear assertions.

How do I prevent overwriting my existing pytest files when generating test coverage?▼

To prevent overwriting existing pytest files, the tool detects an existing tests/test_<module_basename>.py file and stops execution, ensuring your developer work and custom test conventions remain safe.

What is the best way to align generated tests with my project's conftest.py fixtures?▼

The best way to align generated tests with your fixtures is to let the tool read your tests/conftest.py file directly, allowing it to discover available test fixtures and match expected testing approaches.

Can I use this to generate tests for modules without any existing test style exemplar?▼

No, generating tests requires reading one existing style exemplar from your project to ensure the output follows your specific Frood naming conventions and structural patterns accurately.

Why does the generated test coverage focus on deterministic mocks and clear assertions?▼

Generated test coverage focuses on deterministic mocks and clear assertions to prevent fragile or incomplete coverage, ensuring that both sync and async unit tests remain reliable and maintainable.