test-writer

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

خيارات التثبيت

يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.

npx skills add https://github.com/genkit-ai/genkit --skill test-writer

يبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.

تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.

اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.

SKILL.md

تعليمات المصدر · معاينة للقراءة فقط

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.

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.

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.