-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bash completion for chip example applications #36841
Conversation
PR #36841: Size comparison from 9e203e2 to 294b244 Full report (69 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@arkq at a recent SWTT standup we decided to try once again for stricter "require tests".
Could you please add a "testing" section to describe how this were tested. This is likely "manual on bash" however please provider details enough to make it very clear this was tested (including input/output). We are making "manual test" at least somewhat inconvenient to need to type things out otherwise we would get a lot of "this was tested manually" on all PRs to avoid creating tests. Please also add an explanation why this change cannot be tested in an automated fashion.
This PR provides support for most example applications found in the examples folder.
Testing
Why it's not automatically tested? Hmmm... creating a test harness for bash autocompletion seems a bit like an overkill... but of course is doable :D