ScholarGate
Avustaja

Vertaile menetelmiä

Tarkastele valitsemiasi menetelmiä rinnakkain; eroavat rivit korostetaan.

Koodikattavuusanalyysi×Defect Prediction Model×
TieteenalaOhjelmistotekniikkaOhjelmistotekniikka
MenetelmäperheProcess / pipelineProcess / pipeline
Syntyvuosi19882005
KehittäjäTest Coverage CommunityThomas Ostrand, Elaine Weyuker, Robert Bell
Tyyppimeasurement and analysismachine learning model
AlkuperäislähdeZhu, H., Hall, P. A. V., & May, J. H. R. (1997). Software unit test coverage and adequacy. ACM Computing Surveys, 29(4), 366–427. DOI ↗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 ↗
Rinnakkaisnimetcoverage metrics, test coverage, instrumentation-based measurementfault prediction, bug prediction, defect classification
Liittyvät44
Tiivistelmä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.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.
ScholarGateAineisto
  1. v1
  2. 3 Lähteet
  3. PUBLISHED
  1. v1
  2. 3 Lähteet
  3. PUBLISHED

Siirry hakuun Download slides

ScholarGateVertaile menetelmiä: Code Coverage Analysis · Defect Prediction Model. Haettu 2026-06-15 osoitteesta https://scholargate.app/fi/compare