feat(poly test diff): extract related bricks from changed tests - #460
Merged
Conversation
DavidVujic
marked this pull request as draft
August 5, 2026 08:38
DavidVujic
marked this pull request as ready for review
August 6, 2026 08:49
…sting affected bricks feature
…kup by imports/usage or by corresponding brick path
DavidVujic
force-pushed
the
test-diff-related-bricks
branch
from
August 7, 2026 06:33
d4ea600 to
faed46b
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.



Description
Adding the possibility to find related bricks for changed tests. The existing behaviour of the
poly test diffcommand is to inspect the tests, and find bricks by the imports made in the tests.This new feature adds a
--strategypath option to find the corresponding brick according to the folder structure.Example
A changed test in
test/components/my_namespace/my_brick/the_test_for_the_brick.py,the poly tool will look for a corresponding/related brick in
components/my_namespace/my_brick.fixes issue #459
Motivation and Context
The idea and implementation suggestions is from issue #459
How Has This Been Tested?
✅ CI
✅ added unit tests
✅ local run of the
poly test diffcommand.Types of changes
Checklist: