Repository navigation
test: cover indirect unittest discovery and genuine exclusions - #816
Merged
Conversation
…d-discovery-and-actual-ci-execution: cover indirect unittest discovery grounding
|
To preview the documentation for this pull request, visit the following URL:
|
vypbot
self-requested a review
October 30, 2026 19:49
1 task done
Contributor
Bugbot: review complete
|
Contributor
Copilot approval · Human review neededStatus: A protected workflow, policy, or trust-boundary file changed. Technical evidenceRevision: |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #816 +/- ##
===========================================
+ Coverage 94.50% 95.17% +0.67%
===========================================
Files 1035 1104 +69
Lines 33299 36348 +3049
Branches 9824 10852 +1028
===========================================
+ Hits 31468 34594 +3126
+ Misses 699 673 -26
+ Partials 1132 1081 -51 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The reported v3 review incorrectly inferred that indirect unittest discovery never executes a module. The current upstream baseline already keeps the valid paths and detects the real exclusions; this PR adds explicit regression coverage and provenance while preserving production instructions and packaged runtime byte-for-byte.
Closes #806
What changed
Validation
Six focused suites: 216 tests passed; unchanged shared prompt has 100% statements, branches, functions and lines.
Types, lint, specifications, documentation, workflows and agent-doc contracts pass. Graphify is updated; package validation and isolated CLI/API/web smoke pass.
Final CLI hash and production source match the selected measured baseline exactly. Coverage validation retains every existing global/module budget; there is no executable production delta to assign a patch percentage.
Mandatory normal commit hook passes: rebuilt bundles, 814 suites and 15,453 tests passed with 35 existing skips, then lint. Committed build validation passes and the tracked tree is clean.
Review notes
The six-case baseline has zero false positives/negatives but only one of two exact anchors, failing the unchanged location floor. An expanded discovery instruction gives worse anchors and is rejected; its score and complete predictions are retained in
quality/bugbot/evidence/issue-806.json. This is regression coverage for existing grounding, without a claimed model-quality improvement, historical reproduction or consumer adoption. No threshold is lowered.