testing

Codify Python testing best practices for unit and integration tests.

4|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/gigaverse-app/skillet --skill testing-gigaverse-app
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/gigaverse-app/skillet/tree/main/python-standards/skills/testing
Command: npx skills add https://github.com/gigaverse-app/skillet --skill testing-gigaverse-app

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Improve testing quality for Python projects.

Core Features & Use Cases

  • Establishes guidelines for writing, updating, and reviewing tests across unit and integration tests.
  • Enforces TDD workflows, mocking best practices, and invariant-based testing to catch regressions early.
  • Provides reference materials and patterns (fixtures, data models, and test data) to boost consistency and efficiency.

Quick Start

Identify existing fixtures in tests/conftest.py, review sibling test files for patterns, and run pytest with coverage (pytest --cov=src --cov-report=term-missing).

Frequently Asked Questions about testing

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

FAQPage Schema
How do I enforce TDD workflows and invariant checks in Python testing?

You can enforce TDD workflows and invariant checks by applying codified best practices, reference guidelines, and templates to guide consistent test quality and catch regressions early in Python projects.

What are the best practices for mocking and fixtures in pytest?

Mocking and fixture best practices involve using established patterns from reference materials, checking data models, and utilizing tests/conftest.py to boost consistency and efficiency across unit and integration tests.

How do I structure unit and integration tests for consistent test quality?

Structure unit and integration tests by identifying existing fixtures in tests/conftest.py, reviewing sibling test files for patterns, and running pytest with coverage to ensure consistent test quality.

Does this testing approach require specific dependencies or environments?

No specific dependencies are required, as the approach uses a reference set of guidelines, templates, and checks for mocking, data fixtures, concurrency, and test-data standards to guide teams toward consistency.

When should I use invariant-based testing over standard unit tests?

Use invariant-based testing alongside standard unit tests when you need to enforce strict TDD workflows and catch regressions early by verifying that core conditions remain true across various operations.