refactor(tests): neutralize synthetic fixture and parity identifiers - #378
Merged
Merged
Conversation
11 tasks
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
1 participant
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.
Scope
Rename two application regression fixtures that carried unrelated product/vendor branding even though the fixtures are generated by ARSAS test code. The 58-member cross-LD synthetic SCL retains its 22 Analog + 36 Digital members, exact references, CDC/FC relationships and completeness assertions; only file/class/method/header label and synthetic input filename are neutralized. The RCB regression changes only its file/class name.
Provenance boundary
These tests are project-authored synthetic XML/source assertions, not imported third-party fixture assets. Original historical commits and physically accepted evidence remain untouched and findable via Git history. This change makes no assertion about external tools or ownership of other repository assets.
No app/runtime code, real physical evidence JSON, Smart Discovery/SCL/RCB production logic, engine lock, version or released binary changes. Full Windows test suite and current guards must pass.