Summary
graphistry/tests/compute/gfql/cypher/test_m1_differential_scaffold.py still carries an M1-era legacy-vs-candidate differential scaffold. The strict binder/runtime rollout has since landed, so this test harness should be audited for deletion or replacement by direct conformance tests.
Current evidence
On current origin/master:
test_m1_differential_scaffold.py defines _run_legacy() and compares binder-prepass/candidate behavior against legacy behavior.
- Tests include
test_diff_corpus_legacy_baseline and test_diff_corpus_legacy_vs_candidate.
- Other strict binder and runtime parity tests now pin the active paths directly.
Goal
Delete obsolete legacy-baseline scaffolding after confirming its coverage is duplicated by current binder/runtime tests, or replace any unique cases with direct assertions and then delete the scaffold.
Scope
- Inventory each
_DiffCase and map it to current direct tests, or promote missing cases into focused tests.
- Remove
_run_legacy() and candidate-vs-legacy comparison scaffolding if no longer needed.
- Keep only direct behavior tests that assert current intended semantics.
- Record test LOC removed.
Out of scope
- Changing runtime/compiler semantics.
- Reintroducing broad differential framework work.
- Public API deprecation removal.
Acceptance
- Obsolete M1 differential scaffold is deleted or materially reduced.
- Any unique cases are preserved as direct tests.
- Focused Cypher binder/lowering tests pass.
- Full relevant GFQL CI passes.
Related
Summary
graphistry/tests/compute/gfql/cypher/test_m1_differential_scaffold.pystill carries an M1-era legacy-vs-candidate differential scaffold. The strict binder/runtime rollout has since landed, so this test harness should be audited for deletion or replacement by direct conformance tests.Current evidence
On current
origin/master:test_m1_differential_scaffold.pydefines_run_legacy()and compares binder-prepass/candidate behavior against legacy behavior.test_diff_corpus_legacy_baselineandtest_diff_corpus_legacy_vs_candidate.Goal
Delete obsolete legacy-baseline scaffolding after confirming its coverage is duplicated by current binder/runtime tests, or replace any unique cases with direct assertions and then delete the scaffold.
Scope
_DiffCaseand map it to current direct tests, or promote missing cases into focused tests._run_legacy()and candidate-vs-legacy comparison scaffolding if no longer needed.Out of scope
Acceptance
Related