Repository navigation
test: isolate QML stubs and fix test-runner compatibility - #48
Merged
Merged
Conversation
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.
What
Isolate stub QML module descriptors in both test runners and correct integration sandboxing, localization, fixture paths and mutation-fixture signing.
Why
Mixed versioned/unversioned imports can resolve the installed native module instead of test stubs, causing read-only-property errors and native side effects. A targeted qmldir URL interceptor keeps the intended descriptor; a mixed-import regression checks a stub-only property. Production QML remains unchanged. Temporary Git fixtures disable inherited signing locally.
Test plan
474dc8a: conflict-free merge; none of the six contribution files changed upstream.Notes for reviewer
Only test infrastructure changes: CMake integration, shared QML stubs, both runners, integration QML and the mutation fixture script. No production QML import pin, renderer-pointer update or dependency on unpublished renderer code. No full-preflight rerun was necessary for this compatibility audit because no source was updated. Known external sanitizer findings and unavailable live rendering checks remain separate limitations. Draft for upstream review.