ScholarGate
المساعد

قارن الطرق

راجع الطرق التي اخترتها جنبًا إلى جنب؛ الصفوف المختلفة مميَّزة.

التحليل الساكن للتعليمات البرمجية×اختبار التقسيم التكافؤي×
المجالهندسة البرمجياتهندسة البرمجيات
العائلةProcess / pipelineProcess / pipeline
سنة النشأة20011979
صاحب الطريقةDavid Engler and William PughGlenford Myers
النوعautomated analysispartitioning strategy
المصدر التأسيسيChess, B., & West, J. (2007). Secure Programming with Static Analysis. Addison-Wesley Professional. link ↗Myers, G. J. (1979). The Art of Software Testing. John Wiley & Sons. link ↗
الأسماء البديلةstatic analysis, code inspection, automated reviewequivalence partitioning, BVA, boundary value analysis
ذات صلة44
الملخصStatic code analysis automatically examines source code without execution, detecting potential bugs, security vulnerabilities, code smells, and style violations. Pioneered by Engler and Pugh (2001), automated analysis tools scan codebases at scale, identifying defect patterns faster than manual review. Organizations integrate static analysis into continuous integration pipelines to prevent defects early.Equivalence partitioning divides input domains into equivalence classes—sets of inputs expected to behave identically—then selects test cases from each class. Introduced by Myers (1979), this technique reduces test cases while maintaining effectiveness. Boundary value analysis (BVA) complements partitioning by testing values at partition boundaries where failures often occur.
ScholarGateمجموعة البيانات
  1. v1
  2. 3 المصادر
  3. PUBLISHED
  1. v1
  2. 3 المصادر
  3. PUBLISHED

انتقل إلى البحث Download slides

ScholarGateقارن الطرق: Static Code Analysis · Equivalence Partitioning Testing. استُرجع بتاريخ 2026-06-15 من https://scholargate.app/ar/compare