Test-reviewer passes a stub that cannot run the code under test; diff-test stops at the first red step #903
Labels
No labels
P0
P1
P2
P3
bug
category/code-change
category/cross-repo
category/eval-run
category/investigation
category/no-test-target
category/owner-ruling
category/prose-artifact
category/recurring-chore
category/structure
category/umbrella
crc-refactor
create
delete
enhancement
filed-by/agent
filed-by/user
frozen
lint-rule
needs-info
needs-triage
next
plugin/cc-architect
plugin/os
plugin/os-adr
plugin/os-aidd-lint
plugin/os-backlog
plugin/os-context
plugin/os-doc-hygiene
plugin/os-sdlc
plugin/os-vault
project/cc-os
ready-for-agent
ready-for-human
recurring
review
rule-proposal
update
waiting
wayfinder:grilling
wayfinder:map
wayfinder:map
wayfinder:research
wayfinder:task
wayfinder:task
wontfix
worklist/deviations
worklist/lint-rule
worklist/new-implement-build
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jared/cc-os#903
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
The test-reviewer passed a test whose stub cannot run the code under test. The diff-test gate then stops at the first red step, so later failures stay hidden. This is the same pattern as #890 (#878). Parent: #859.
Observed
In #880 implementation 2,
tests/presenter/brief_drafted_map_test.rbusedFacts = Struct.new(:reports)with no#fact.Brief#composeraised NoMethodError. The test-reviewer (dispatch 7) passed it.Three programmer-repair dispatches could not fix it, because programmers may not edit tests. They never saw 3 further failures in
tests/command/implementation/open_map_name_test.rb, because the diff-test gate stops at the first red step.Reproduce
n/a: decompose decides the reproduction. The evidence is implementation 2 of #880 (hand-fixed in
c585e62c).Approach
Decide in decompose how the test-reviewer detects a stub that cannot run the code under test, and whether the diff-test gate reports every red step.
Origin
c585e62c.Duplicate check against #890: NOT a duplicate. Leaving open.
What #890 covers: the stub defect. #890's revised approach lets the programmer escalate a defective test on gate-sourced nodes, so the repair-bound burn this ticket describes stops.
What remains (not covered by #890):
32 runs, ... 1 errors;open_map_name_test.rbwas never in the selection.Project::Changes#test_paths(query/project/changes.rb:15-16) maps tests by name only, andDiffTestPlan#widened?(model/diff_test_plan.rb:24-25) widens to the suite only when no test maps at all. So the unmappedmodel/map.rbandmodel/map/headers.rbdid not widen the run.Suggested re-scope: retitle to the diff-test selection gap, with ADR-0202 as the reference.