test: rename sample.yaml to tests.yaml and namespace twister scenarios#54
Merged
Conversation
Follow upstream filename unification (example-application#102). Scenario names are now unique per app since twister keys suites by bare scenario name globally, and rasprover's integration platform is fixed to the fully qualified ros_driver/esp32/procpu. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Summary
sample.yaml→tests.yamlin all four apps, following upstream filename unification (Rename sample.yaml and testcase.yaml files to tests.yaml zephyrproject-rtos/example-application#102). The pinned Zephyr's twister already accepts the new name.app.default→app.<app>.default): twister now keys suites by bare scenario name globally, so the duplicatedapp.defaultacross apps raisedDuplicate test suiteerrors.integration_platformsto the fully qualifiedros_driver/esp32/procpu(bareros_driverwas rejected as an unrecognized platform).example-application→pico-fw).Testing
uv run west twister --list-tests -T applicationsdiscovers all 7 scenarios with no errors.🤖 Generated with Claude Code