test

Run targeted pytest unit tests with coverage and parallel execution.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/prata0x/gfo --skill test-prata0x
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test
Source: https://github.com/prata0x/gfo/tree/main/.claude/skills/test
Command: npx skills add https://github.com/prata0x/gfo --skill test-prata0x

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly run focused unit tests inside a repository by orchestrating pytest with targeted filters, coverage, and parallel execution, saving time during development.

Core Features & Use Cases

  • Selective test execution by file path, class, function, or keyword (e.g., tests/test_commands/test_pr.py::TestPrList or -k "test_create")
  • Parallel test execution with pytest-xdist (-n auto) for faster feedback
  • Coverage reporting with --cov=gfo and --cov-report=term-missing to surface gaps

Quick Start

Run the targeted unit tests under tests/ (excluding tests/integration) with coverage and parallelism using pytest, for example with: python -m pytest {target} --cov=gfo --cov-report=term-missing -n auto

Frequently Asked Questions about test

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

FAQPage Schema
How do I run specific pytest unit tests by file or function name while skipping integration tests?

Run specific pytest unit tests by file, class, function, or keyword using explicit target filters. The execution automatically excludes integration tests, ensuring only focused unit tests run during development.

What is the best way to speed up pytest execution for a large Python project?

Speed up pytest execution by enabling parallel test runs with pytest-xdist using the -n auto flag. This distributes tests across multiple CPU cores to provide faster feedback during development.

Can I generate pytest coverage reports for missing lines when running targeted tests?

Generate pytest coverage reports for missing lines by applying --cov=gfo and --cov-report=term-missing. This surfaces coverage gaps directly in the terminal output after the targeted test run.

Does this pytest automation approach work with keyword-based test selection?

This pytest automation approach works with keyword-based test selection using the -k flag. You can target specific tests like -k "test_create" to run focused unit tests matching that keyword expression.

Why should I exclude integration tests when running unit tests in a Python repository?

Exclude integration tests when running unit tests to maintain fast feedback loops during development. This approach enforces explicit targets and automatically filters out integration tests to keep execution focused and rapid.