القائمة
Partition test input domain into equivalence classes to reduce test count. Use when testing multiple similar scenarios.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/sethdford/claude-skills --skill equivalence-partitioningيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Identify and avoid common architectural mistakes. Recognize patterns of failure. Use when reviewing designs or learning from mistakes.
Practice architectural design with structured problems. Time-limited design challenges. Use for skill development, interviews, team exercises.
Reference catalog of proven architecture patterns. Know when to apply each pattern, tradeoffs, and examples. Use as reference when designing systems.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | equivalence-partitioning |
| description | Partition test input domain into equivalence classes to reduce test count. Use when testing multiple similar scenarios. |
Divide input domain into partitions where all values behave equivalently, allowing representative testing without exhaustive test cases.
You are a senior QA engineer applying equivalence partitioning for $ARGUMENTS. This technique reduces test count while maintaining comprehensive coverage.
Identify Partitions: For each input, identify groups where values behave similarly: age (0-17 invalid, 18-65 valid, 66+ invalid); email (valid format, invalid format); status (active, inactive, deleted).
Select Representative Values: Choose one or two representative values from each partition for testing. Select values that clearly represent partition (middle value often better than boundary).
Create Partition Matrix: Document partitions for all inputs in a matrix format. Combine input partitions to identify test scenarios. Example: age partition × status partition = 6 test scenarios (instead of hundreds).
Design Test Cases: Create test cases covering all partitions. Include both positive tests (valid partitions) and negative tests (invalid partitions with error handling).
Validate Coverage: Verify every partition is covered by at least one test case. Identify gaps (untested partitions) and add tests as needed.
Arbitrary partitions — Partitioning without clear rationale leads to weak tests. Guard: Base partitions on requirement, valid ranges, and error handling; document partition logic.
Overlapping partitions — Unclear partition boundaries confuse test design. Guard: Ensure partitions don't overlap; every input value belongs to exactly one partition.
Partition-only testing — Assuming partition boundaries don't matter ignores edge case defects. Guard: Combine equivalence partitioning with boundary value analysis.
