本文へ移動
cccskills
無料GitHub で公開

python-testing

Test Python services with pytest, async coverage, monkeypatch, and boundary-focused fakes. Use when writing Python tests, fixtures, async tests, regression tests, or dependency-isolated verification.

インストール方法を見る

含まれるファイル(3)

  • SKILL.md3.3 KB
  • evals/evals.json1.2 KB
  • references/pytest-patterns.md475 B

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Python Testing

Priority: P0 (CRITICAL)

Core Rule Anchors

  • [BE-TEST-01] Parametrized Tests for Equivalent Inputs: Prefer pytest.mark.parametrize for equivalent inputs and boundary permutations. Distinct scenarios may stay separate.
  • [BE-TEST-02] Ban on Brittle SQL String Matching: Test pure domain calculations directly or use fakes/testcontainers; do not regex-match SQL strings in mocks.
  • [BE-TEST-03] Ban on Shallow Assertions: Never assert only assert result without inspecting domain attributes and invariants.
  • [BE-TEST-04] Ban on Pass-Through Seam Mocks: Repositories and adapters must test contract compliance and error mapping; ban 1:1 pass-through mock echoing.
  • [BE-TEST-05] Bug-First Regression Lock: Every PR fixing a bug ticket or with title fix(...) must introduce a failing test reproducing the defect before fixing it.

Rules

  • Use pytest and pytest-asyncio for async boundaries.
  • Add regression tests around contract parsing, workflow routing, and verifier outcomes ([BE-TEST-05]).
  • Prefer pytest.mark.parametrize for equivalent inputs; distinct scenarios may stay separate ([BE-TEST-01]).
  • Prefer fakes or monkeypatch at external seams: DB, RPC, Telegram, subprocess, Docker ([BE-TEST-02], [BE-TEST-04]).
  • Verify behavior and domain invariants, not shallow truthiness or implementation trivia ([BE-TEST-03]).
  • Coverage is diagnostic and project-configured; verify risk-weighted critical paths rather than padding code for an arbitrary percentage.

Recipe

  1. Write the failing test first for the boundary or regression ([BE-TEST-05]).
  2. Patch one seam high enough to keep the test readable ([BE-TEST-04]).
  3. Assert structured outcomes: metadata, route result, blocker text, emitted command ([BE-TEST-03]).
  4. Use async tests for async code; avoid spinning real event loops manually.
  5. Cover negative paths for malformed packets, stale runtime state, and missing env.

Anti-Patterns

  • [BE-TEST-01] Stylistic parametrize rewrites: Do not demand parameterized rewrites of passing tests without a behavioral gap.
  • [BE-TEST-02] SQL regex matching: Do not regex-match SQL strings in mocks.
  • [BE-TEST-03] Shallow assertions: Never assert only assert result; always verify domain attributes and invariants.
  • [BE-TEST-04] Pass-through seam mocks: Ban 1:1 mock echoing without contract assertions.
  • [BE-TEST-05] Bug fix without reproduction test: Ban bug fixes without a reproduction test.
  • No live network or DB in unit tests: Use fakes or testcontainers.
  • No broad monkeypatch spray: Patch the boundary, not every helper under it.
  • No smoke-only proof for shared runtime changes: Add focused assertions too.

References

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.

日本語の概要は準備中です。原文の説明を表示しています。

HoangNguyen0403/agent-skills-standard5732026年10月11日 更新

Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow implementation to their specific skills.

日本語の概要は準備中です。原文の説明を表示しています。

HoangNguyen0403/agent-skills-standard5732026年10月11日 更新

Implement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers; defer FCM and notification delivery to android-notifications.

日本語の概要は準備中です。原文の説明を表示しています。

HoangNguyen0403/agent-skills-standard5732026年10月11日 更新

Build high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects; defer deep-link and navigation routing to android-navigation.

日本語の概要は準備中です。原文の説明を表示しています。

HoangNguyen0403/agent-skills-standard5732026年10月11日 更新

Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.

日本語の概要は準備中です。原文の説明を表示しています。

HoangNguyen0403/agent-skills-standard5732026年10月11日 更新

Write correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes, persistence/notifications, and unit-test recipes to their specific skills.

日本語の概要は準備中です。原文の説明を表示しています。

HoangNguyen0403/agent-skills-standard5732026年10月11日 更新

HoangNguyen0403 のスキルをすべて見る

このスキルの問題を報告する