Comparar métodos
Revisa los métodos seleccionados uno junto a otro; las filas que difieren aparecen resaltadas.
| Particionamiento por equivalencia× | Análisis estático de código× | |
|---|---|---|
| Campo | Ingeniería de software | Ingeniería de software |
| Familia | Process / pipeline | Process / pipeline |
| Año de origen≠ | 1979 | 2001 |
| Autor original≠ | Glenford Myers | David Engler and William Pugh |
| Tipo≠ | partitioning strategy | automated analysis |
| Fuente seminal≠ | Myers, G. J. (1979). The Art of Software Testing. John Wiley & Sons. link ↗ | Chess, B., & West, J. (2007). Secure Programming with Static Analysis. Addison-Wesley Professional. link ↗ |
| Alias | equivalence partitioning, BVA, boundary value analysis | static analysis, code inspection, automated review |
| Relacionados | 4 | 4 |
| Resumen≠ | 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. | 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. |
| ScholarGateConjunto de datos ↗ |
|
|