विधियों की तुलना करें
चुनी हुई विधियों की आमने-सामने समीक्षा करें; भिन्नता वाली पंक्तियाँ रेखांकित हैं।
| स्थैतिक कोड विश्लेषण× | समतुल्यता विभाजन परीक्षण (Equivalence Partitioning Testing)× | |
|---|---|---|
| क्षेत्र | सॉफ्टवेयर इंजीनियरिंग | सॉफ्टवेयर इंजीनियरिंग |
| परिवार | Process / pipeline | Process / pipeline |
| उद्भव वर्ष≠ | 2001 | 1979 |
| प्रवर्तक≠ | David Engler and William Pugh | Glenford Myers |
| प्रकार≠ | automated analysis | partitioning 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 review | equivalence partitioning, BVA, boundary value analysis |
| संबंधित | 4 | 4 |
| सारांश≠ | 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डेटासेट ↗ |
|
|