القائمة
Prioritize test efforts based on risk assessment. Use when allocating limited testing resources to maximize defect detection.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/sethdford/claude-skills --skill risk-based-test-planيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى 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 | risk-based-test-plan |
| description | Prioritize test efforts based on risk assessment. Use when allocating limited testing resources to maximize defect detection. |
Systematically identify, assess, and prioritize risks to allocate test effort where it matters most.
You are a senior QA engineer helping create a risk-based test plan for $ARGUMENTS. Risk assessment guides test prioritization, ensuring critical areas receive appropriate scrutiny.
Identify Risk Sources: Map potential failure sources across functional areas, integrations, third-party dependencies, performance-critical paths, and security-sensitive components. Consider both known and emerging risks based on system complexity and team experience.
Assess Risk Probability and Impact: For each risk, estimate likelihood of occurrence (rare, low, medium, high) and impact if it occurs (insignificant, minor, major, critical). Combine dimensions into a risk matrix (probability × impact).
Prioritize by Risk Level: Sort identified risks by severity (critical, high, medium, low). Allocate test effort proportionally: critical risks receive comprehensive testing; low risks receive minimal testing or deferral. Document risk assumptions and rationale.
Design Risk-Mitigation Tests: For each high/critical risk, design specific tests that would detect the potential failure. Include multiple test techniques (unit, integration, system, exploratory) to reduce residual risk.
Track and Adjust: Monitor test execution against risk prioritization. If high-priority areas reveal fewer defects than expected, reassess risk assumptions. If low-priority areas reveal unexpected defects, re-prioritize future testing.
Vague risk definitions — Saying "performance is risky" without specific thresholds or scenarios prevents effective mitigation. Guard: Define risks concretely with measurable criteria (e.g., "response time >500ms under 1000 concurrent users").
Static risk assessment — Treating risk as fixed ignores new information from testing and development. Guard: Review risk assessment mid-project; adjust as code changes, new dependencies emerge, or test results shift expectations.
Ignoring unknown unknowns — Focusing only on identified risks misses novel failure modes. Guard: Reserve 10-15% of testing time for exploratory testing to discover unplanned risks.
