विधियों की तुलना करें
चुनी हुई विधियों की आमने-सामने समीक्षा करें; भिन्नता वाली पंक्तियाँ रेखांकित हैं।
| कोड कवरेज विश्लेषण× | समतुल्यता विभाजन परीक्षण (Equivalence Partitioning Testing)× | |
|---|---|---|
| क्षेत्र | सॉफ्टवेयर इंजीनियरिंग | सॉफ्टवेयर इंजीनियरिंग |
| परिवार | Process / pipeline | Process / pipeline |
| उद्भव वर्ष≠ | 1988 | 1979 |
| प्रवर्तक≠ | Test Coverage Community | Glenford Myers |
| प्रकार≠ | measurement and analysis | partitioning strategy |
| मौलिक स्रोत≠ | Zhu, H., Hall, P. A. V., & May, J. H. R. (1997). Software unit test coverage and adequacy. ACM Computing Surveys, 29(4), 366–427. DOI ↗ | Myers, G. J. (1979). The Art of Software Testing. John Wiley & Sons. link ↗ |
| उपनाम | coverage metrics, test coverage, instrumentation-based measurement | equivalence partitioning, BVA, boundary value analysis |
| संबंधित | 4 | 4 |
| सारांश≠ | Code coverage analysis measures the extent to which source code is executed by a test suite, quantifying which lines, branches, or paths are exercised. Tools instrument code to track execution, reporting coverage percentages and identifying untested regions. Coverage analysis guides test creation, detects dead code, and validates test adequacy in quality assurance processes. | 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डेटासेट ↗ |
|
|