-
Notifications
You must be signed in to change notification settings - Fork 2.1k
tools: improve testrunner #7258
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
Conversation
I'll be rebuilding this a lot. :) |
Will there also be a way to say: "need 3 nodes, two must have IEEE 802.15.4"? |
How does a board "have 6LoWPAN"? |
Sure! This is implemented using simple tags. |
But don't you mean it "has an IEEE 802.15.4 radio"? I'm not sure if there are already 6LoWPAN-integrated devices ;). |
I badly misquoted. :) Yeah, specifying 802.15.4 instead of sixlowpan makes a lot more sense. Luckily tag names can be freely chosen. :) |
f5c690e
to
b70d771
Compare
…ner support to murdock script
I guess this is superseded by #8801 now? If not, just reopen. |
Nope, they're complementary. But I'll reopen when there are news. |
This PR finally adds a way of flexibly run tests on real hardware.
Before, there was "testrunner", which could sequentially run tests on a single board, and the beginnings of a more general approach, hidden in lwip's tests.
Testrunner can now read json files (or whole trees of them) containing test and node descriptions.
Test descriptions describe things like "need 3 nodes, two of them samr21-xpro, one of them must have 6lowpan; flash gnrc_networking on the first, gnrc_border_router on the second and nanocoap_test on the third; set up the default route of the first and third to be the link local address of the second; then run these pexpect scripts; .....".
Node descriptions describe node groups of actual nodes, like "node0 is a samr21-xpro, serial number ATMLxxxx, has 6lowpan and a mma8x5x connected, node 1 is ...". The latter can be less specific if they contain a field "murdock_queue".
There are some nifty features (including files, simple templateing) in order to reduce duplication in the description files.
The testrunner can then read in a bunch of test and node descriptions, and then run tests, either every test once, or every test on each node group that can run it. It can also create command lines usable by murdocks backend DWQ.
Another commit adds initial integration into murdock.
Currently, there's only one samr21-xpro connected to my laptop, for testing.
TODO:
DO NOT MERGE! This is WIP.