Comparer des méthodes
Examinez les méthodes sélectionnées côte à côte ; les lignes qui diffèrent sont mises en évidence.
| Analyse statique de code× | Test de partitionnement par équivalence× | |
|---|---|---|
| Domaine | Génie logiciel | Génie logiciel |
| Famille | Process / pipeline | Process / pipeline |
| Année d'origine≠ | 2001 | 1979 |
| Auteur d'origine≠ | David Engler and William Pugh | Glenford Myers |
| Type≠ | automated analysis | partitioning strategy |
| Source fondatrice≠ | 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 ↗ |
| Alias | static analysis, code inspection, automated review | equivalence partitioning, BVA, boundary value analysis |
| Apparentées | 4 | 4 |
| Résumé≠ | 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. |
| ScholarGateJeu de données ↗ |
|
|