Repository navigation
Check regression coverage for added tests - #2748
Merged
Merged
Conversation
joelhawksley
force-pushed
the
joelhawksley-regression-test-ci
branch
from
October 26, 2026 19:17
f8de78a to
da3b10a
Compare
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.
Run added and modified Minitest tests with and without a pull request's packaged implementation changes. Informational by default; the
regression-testlabel opts into strict enforcement.Audited the latest 100 pull requests before opening this one (#2747–#2643): 325 tests across 30 pull requests. 34 demonstrated a regression, 41 also passed without the implementation, 248 were inconclusive, and 2 failed on the historical head. All dependency setups completed.
The audit correctly reproduces #2747. It also flags #2710—the change that introduced that regression—as having no added or modified selectable Minitest tests. The 41 passing-on-base cases are review candidates, not confirmed coverage bugs. Most inconclusive cases involve pre-fix boot errors or unavailable APIs.
Includes a resumable
script/regression_check_history.rbaudit command and per-test JSON/log artifacts. The new hosted job, Ruby/Rails test matrix, and CodeQL pass.