ScholarGate
Assistant

Comparer des méthodes

Examinez les méthodes sélectionnées côte à côte ; les lignes qui diffèrent sont mises en évidence.

Test de partitionnement par équivalence×Modèle de prédiction de défauts×
DomaineGénie logicielGénie logiciel
FamilleProcess / pipelineProcess / pipeline
Année d'origine19792005
Auteur d'origineGlenford MyersThomas Ostrand, Elaine Weyuker, Robert Bell
Typepartitioning strategymachine learning model
Source fondatriceMyers, G. J. (1979). The Art of Software Testing. John Wiley & Sons. link ↗Ostrand, T. J., Weyuker, E. J., & Bell, R. M. (2005). Predicting the location and number of faults in large software systems. IEEE Transactions on Software Engineering, 31(4), 340–355. DOI ↗
Aliasequivalence partitioning, BVA, boundary value analysisfault prediction, bug prediction, defect classification
Apparentées44
Résumé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.Defect prediction models forecast the likelihood of software faults in code modules using statistical or machine learning approaches. Pioneered by Ostrand, Weyuker, and Bell (2005), these models correlate code metrics (complexity, churn, coupling) with historical defect data to identify high-risk components. Organizations use predictions to allocate testing resources, guide code review, and prioritize refactoring.
ScholarGateJeu de données
  1. v1
  2. 3 Sources
  3. PUBLISHED
  1. v1
  2. 3 Sources
  3. PUBLISHED

Aller à la recherche Télécharger les diapositives

ScholarGateComparer des méthodes: Equivalence Partitioning Testing · Defect Prediction Model. Consulté le 2026-06-15 sur https://scholargate.app/fr/compare