Сравнение методов
Просматривайте выбранные методы рядом; строки с различиями подсвечены.
| Статический анализ кода× | Тестирование методом разбиения на эквивалентные классы× | |
|---|---|---|
| Область | Программная инженерия | Программная инженерия |
| Семейство | 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Набор данных ↗ |
|
|