test-writer

スター6,291

フォーク807

更新日2026年6月4日 02:15

How to write pytest tests for modules in this workspace. Load whenever you are about to write or extend tests.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

ソース

genkit-ai

genkit-ai/genkit

ダウンロード

Test writer

When writing pytest tests in this workspace:

One test file per module. foo.py lives next to foo_test.py (suffix, not prefix).
Cover the happy path AND at least one edge case. Empty input, duplicates, boundary values — pick what matters for the unit under test.
Use pytest.mark.parametrize when the same assertion runs over a small table of inputs. Keep IDs descriptive.
Name tests test_<unit>_<scenario>_<expected>. Examples: test_total_empty_cart_returns_zero, test_add_duplicate_item_merges_quantities.
Arrange / Act / Assert. Three clear blocks. No setup hidden in fixtures unless it's reused across at least two tests.
Assert behavior, not implementation. Don't reach into private attributes or count function calls; check the observable result.
Imports at module top. Don't import inside test functions.

このリポジトリの他の Skills

同じリポジトリ

TypeScript coding conventions, best practices, and patterns for writing clean, maintainable code.

Conventions for clean, idiomatic Python. Load whenever you read, edit, or write Python source files.

Explain concepts in very simple terms suitable for a five-year-old.

Respond as a single traditional haiku with a 5-7-5 syllable structure.

Respond in the voice of a swashbuckling pirate.

Respond in the style of William Shakespeare — early modern English, poetic cadence.

name	test-writer
description	How to write pytest tests for modules in this workspace. Load whenever you are about to write or extend tests.

When writing pytest tests in this workspace:

One test file per module. foo.py lives next to foo_test.py (suffix, not prefix).
Cover the happy path AND at least one edge case. Empty input, duplicates, boundary values — pick what matters for the unit under test.
Use pytest.mark.parametrize when the same assertion runs over a small table of inputs. Keep IDs descriptive.
Name tests test_<unit>_<scenario>_<expected>. Examples: test_total_empty_cart_returns_zero, test_add_duplicate_item_merges_quantities.
Arrange / Act / Assert. Three clear blocks. No setup hidden in fixtures unless it's reused across at least two tests.
Assert behavior, not implementation. Don't reach into private attributes or count function calls; check the observable result.
Imports at module top. Don't import inside test functions.