← All research studies

Defects4J · Completed method investigation

When the score cannot support the risk target.

A completed development audit asks whether a software-bug scorer has enough signal to justify a protected calibration experiment.

Development auditAggregate results

Audit outcome

Insufficient signal

No supported threshold in the fixed development procedure.

Protected calibration

Not run

The development finding stopped progression.

Protected test access

0

No locked outcomes were used.

A calibration method cannot manufacture a useful ranking from inadequate evidence. A negative readiness result is a scientific result, not a successful validation claim.

What we tested

The fixed development procedure evaluated whether the scorer and action definition could support a certified threshold. It found none and retained all cases for review. No post-audit tuning or protected-use model training followed.

What we found

Completed development audit, not an end-to-end benchmark validation
StageRecorded result
Method engineVerified
Development representationProvenance verified
Scorer signalInsufficient
Protected calibrationNot executed
Locked evaluationNot executed

Keeping this boundary prevents an implemented method from being presented as a demonstrated automation benefit.

What the evidence supports

No protected calibration certificate was produced. The result is a negative development feasibility audit, explicitly separate from the twelve completed benchmark studies.

The statistical statement, in more detail

Development readiness, mathematical method verification and successful held-out validation are different forms of evidence. Passing an implementation check does not establish a scientifically effective scoring signal.

Observed evaluation error, calibration support and practical output size measure different things. The study’s declared population and reference determine how its result should be read.

Scope of the result

The finding concerns this scorer, representation and action design. It is not a claim that software defect prediction cannot be calibrated. No protected calibration or locked-test source/outcome access occurred.

Sources & data

This summary draws on the completed experiment records. The downloadable table contains the aggregate results shown here. A standalone public reproduction package for this investigation is not linked.

Download the result table (CSV)

Numbers are rounded for reading. These are research results, not measured customer outcomes. Dataset examples and individual records are not redistributed on this page.