test: add offline GitLab corpus verification#43
Draft
ebihara99999 wants to merge 1 commit into
Draft
Conversation
Vendor the issue #41 GitLab CE corpus with license attribution and run it through offline RSpec checks. The corpus spec verifies crash-free per-file measurement, report shape, summary derivation, line ranges, method metric count alignment, and sequential/parallel determinism.
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.
Purpose
Refs #41. This adds the first CI layer from the corpus verification plan: vendored corpus files, a per-file runner, crash checks, and metric-agnostic invariants.
RuboCop differential checks and golden snapshots are intentionally left for follow-up PRs.
Changes
85ed8239cfc6fe3cf5d5bde5975fe2f6d687ff6dunderspec/fixtures/corpus/gitlab/.ee/,jh/,doc/exclusion rule.summary.spec/fixtures/**/*_spec.rbfrom RSpec discovery so vendored GitLab spec files remain corpus input data.Impact
This is test-only. The corpus is under
spec/fixtures/, remains outside the packaged gem, and is already outside RuboCop's scan by the repository configuration.Verification
bundle exec rspec- 75 examples, 0 failuresbundle exec rubocop- 34 files inspected, no offensesgit diff --cached --check- no whitespace errors before commitScope Out