Adding docs for the testing process for mbed OS 5 #2364
Conversation
|
Not sure I'll have time to review today; will transclude it into the handbook if you want (information with typos is better than no information) |
|
LGTM. @bridadan happy to link from mbed CLI docs about testing to the testing section in these docs? |
| @@ -0,0 +1,187 @@ | |||
| # Testing in mbed OS 5 | |||
|
|
|||
| The way tests are ran and compiled in mbed OS 5 is substantially different than in previous versions of mbed. Previously tests were located in one known location and a python file was kept (`tools/tests.py`) keeping track of their dependencies, capabilities, and configurations. mbed OS 5 has adopted a more distributed approach to testing. Now test code lives alongside the test code, and these are dynamically discovered by the test tools. | |||
There was a problem hiding this comment.
"are run"
"different from previous"
"Previously, tests were"
"Python file (tools/tests.py) kept track"
"Test code lives alongside the application code"
|
@iriark01 Thanks a lot for looking at this today! I'll get cracking on these fixes |
|
@iriark01 I've made the changes! Everything I 👍ed I made the change you suggested. There were only a couple ones that I didn't make your exact change. I asked your opinion on those, so if you want me to change em let me know! |
|
@screamerbg Sure thing, will do when this is merged |
This adds documentation describing how tests are built and ran within mbed OS 5.
This doesn't cover the mbed CLI commands, but rather the underlying build and test runner process that's occurring when making the calls to mbed CLI and the underlying scripts.
It also describes how to debug tests with IDEs in conjunction with the test tools.
Please review @iriark01
FYI @mazimkhan @adbridge