Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
jorgealves avatar

Python Testing Strategist

  • 149 installs
  • 2 repo stars
  • Updated January 25, 2026
  • jorgealves/agent_skills

Design a layered pytest strategy with fixtures, markers, coverage targets, and CI gates for a Python service or library before merge or release.

About

Helps Python teams architect testing strategy: pick frameworks, structure directories, design fixtures and markers, set coverage goals, and wire CI so agents and developers ship reliable pytest suites for APIs, CLIs, and libraries.

  • Chooses unit, integration, and contract test boundaries
  • Defines pytest fixtures, parametrization, and markers
  • Sets coverage thresholds and flaky-test policies
  • Aligns CI matrix with supported Python versions
  • Documents mocking rules for IO and external APIs

Python Testing Strategist by the numbers

  • 149 all-time installs (skills.sh)
  • +8 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #888 of 2,153 Testing & QA skills by installs in the Skillselion catalog
  • Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/jorgealves/agent_skills --skill python-testing-strategist

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs149
repo stars2
Last updatedJanuary 25, 2026
Repositoryjorgealves/agent_skills

What it does

Design a layered pytest strategy with fixtures, markers, coverage targets, and CI gates for a Python service or library before merge or release.

Files

SKILL.mdMarkdownGitHub ↗

Python Testing Strategist

Purpose and Intent

Design comprehensive Python test suites including unit, integration, and E2E tests. Use when establishing testing patterns for new or existing Python applications.

When to Use

  • Project Setup: When initializing a new Python project.
  • Continuous Integration: As part of automated build and test pipelines.
  • Legacy Refactoring: When updating older Python codebases to modern standards.

When NOT to Use

  • Non-Python Projects: This tool is specialized for the Python ecosystem.

Error Conditions and Edge Cases

  • Missing Requirements: If the project lacks a requirements.txt or pyproject.toml.
  • Incompatible Versions: If the project uses a Python version not supported by the tools.

Security and Data-Handling Considerations

  • All analysis is performed locally.
  • No source code or credentials are ever transmitted externally.

Related skills

Testing & QAtestingbackenddevops

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.