Confronta i metodi
Esamina i metodi selezionati fianco a fianco; le righe che differiscono sono evidenziate.
| Partizionamento per Classi di Equivalenza× | Analisi della copertura del codice× | |
|---|---|---|
| Campo | Ingegneria del software | Ingegneria del software |
| Famiglia | Process / pipeline | Process / pipeline |
| Anno di origine≠ | 1979 | 1988 |
| Ideatore≠ | Glenford Myers | Test Coverage Community |
| Tipo≠ | partitioning strategy | measurement and analysis |
| Fonte seminale≠ | Myers, G. J. (1979). The Art of Software Testing. John Wiley & Sons. link ↗ | 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 ↗ |
| Alias | equivalence partitioning, BVA, boundary value analysis | coverage metrics, test coverage, instrumentation-based measurement |
| Correlati | 4 | 4 |
| Sintesi≠ | 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. | 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. |
| ScholarGateInsieme di dati ↗ |
|
|