test

...

Updated May 24, 2025

Search Tags:#testing #pytest #coverage #quality-assurance #test #continuous-integration

Ready to run

npx skills add https://github.com/lemeb/python-library-cookiecutter --skill test-lemeb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test
Source: https://github.com/lemeb/python-library-cookiecutter/tree/main/%7B%7Bcookiecutter.project_slug%7D%7D/.claude/skills/test
Command: npx skills add https://github.com/lemeb/python-library-cookiecutter --skill test-lemeb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures that any new code added is properly tested to prevent regressions by enforcing 100% test coverage.

Core Features & Use Cases

Run coverage checks on new changes to identify gaps in tests.
Automatically guide the addition of tests to achieve full coverage before committing.
Integrate into development workflows to catch untested code paths during review.

Quick Start

Run make test-with-coverage to verify your changes and ensure 100% coverage before committing.

Frequently Asked Questions about test

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

FAQPage Schema

How do I enforce 100% test coverage for new code changes?▼

To enforce 100% test coverage for new code, run coverage checks during development to identify untested paths and guide writing tests before commits. This validates that new changes are fully tested to prevent regressions.

How do I check test coverage gaps using git diff?▼

You can check test coverage gaps by analyzing git diff for new files and re-running tests until the changed code is fully covered. This process identifies untested paths in your new changes before committing.

What is the best way to integrate test coverage checks into code review?▼

The best way to integrate test coverage checks into code review is to run make test-with-coverage to catch untested code paths during the review process. This ensures any new code added is properly tested before merging.

Does pytest work with continuous integration for coverage checks?▼

Yes, pytest works with continuous integration for coverage checks by running make test-with-coverage to validate changes and ensure 100% coverage before committing. This integration catches untested code paths during development and review.

Why does my new code fail the test coverage check?▼

Your new code fails the test coverage check because it contains untested paths that have not reached 100% coverage. The tool analyzes git diff for new files and re-runs tests until the changed code is fully covered.

Can I use this to guide writing tests before commits?▼

Yes, you can use this to automatically guide the addition of tests to achieve full coverage before committing. It validates that new code is properly tested by identifying gaps and re-running tests until complete coverage is achieved.