|
Three ways a same-technology uplift could come out PROVEN too easily:
- The baseline came from a table someone typed. It now counts as measured
only when the script can read per-test results (JUnit or TRX XML, a runner
log with a summary line, or per-test JSON) from analysis/<system>/baseline/
or a "Recorded:" line of BASELINE.md; a counts-only file is ignored, two
measured sources that disagree are a gap, and the typed table must match
what was measured.
- Tests edited during the uplift passed unnoticed. The pack now compares the
legacy and working-copy test files (by walking files only) and lists what
was added, removed or changed; a removed file, more than a quarter of the
files changed, or no legacy tests to compare with is a gap, and it says
plainly that weakened assertions cannot be detected.
- A silent behavioral change with no test at its site. Each Behavioral-silent
delta in the catalog must have a test file naming its site file, or the
module is at most PARTLY PROVEN.
The report's Proof section shows the three new checks, and an uplift pack that
lacks any of them reads as PARTLY PROVEN. 214 script tests pass.
|