scripts: twister: Add test plan filtering feature (--exclude-plan) #79188
+951
−2
Conversation
This file contains 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
golowanow
force-pushed
the
twister_exclude_plan_20240921
branch
2 times, most recently
from
305a364 to
89eb3bc
Compare
zephyrbot
requested review from
gchwier,
hakehuang,
KamilxPaszkiet,
LukaszMrugala,
nashif and
PerMac
|
^ dear reviewers, up to your attention |
|
I am not sure I understand what this PR is trying to do, please provide some more details in form of docs or in the body of this PR. |
|
This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time. |
golowanow
added
In progress
New Twister `exclude-plan` feature for test plan advanced filtering and test scope gap resolution. The new feature allows to apply Twister testplan and report JSON file(s) as extended rules to filter out tests on the following Twister executions. This way a test plan hierarchy can be orchestrated, for example with simulated and physical platforms to optimize their usage. The testplan files can be applied for filtering in different ways: by exact match on test name, platform, runnable status, test status, and their combinations. New Twister options (also documented in command line help): --exclude-plan-exact --exclude-plan-platform --exclude-plan-run --exclude-plan-name --exclude-plan-status Twister test suites for the new feature. Signed-off-by: Dmitrii Golovanov <[email protected]>
golowanow
force-pushed
the
twister_exclude_plan_20240921
branch
from
89eb3bc to
ab79403
Compare
golowanow
added
Enhancement
hakehuang
approved these changes
Jan 19, 2025
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.
New Twister
exclude-planfeature for test plan advanced filtering and test scope gap resolution.The new feature allows to apply Twister test plan and report JSON file(s) as extended rules to filter out tests on the following Twister executions. This way a test plan hierarchy can be orchestrated, for example to chain simulated and physical platforms to optimize their usage.
The test plan files can be applied for filtering in different ways: by exact match on test name, platform, runnable status, test status, and their combinations.
New Twister options (also documented in command line help):
--exclude-plan-exact
--exclude-plan-platform
--exclude-plan-run
--exclude-plan-name
--exclude-plan-status
Twister test suite for the new feature.
Should facilitate #78403