-
Notifications
You must be signed in to change notification settings - Fork 2.1k
tests: introduce dedicated gnrc_rpl_srh
test
#10392
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
gnrc_rpl_srh
testgnrc_rpl_srh
test
99b638c
to
dc7012b
Compare
Rebased to current dependencies |
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
876871d
to
799d943
Compare
Rebased to current master and dependencies. |
8d08640
to
aea29a3
Compare
Rebased to and tested for current master and dependencies. |
aea29a3
to
596a136
Compare
Rebased to current master and dependencies. |
596a136
to
0a72b98
Compare
Rebased to current master and dependencies. |
@miri64 could you squash? |
4201f3d
to
3ff2edf
Compare
Squashed |
Murdock and Travis are happy. |
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.
ACK
So this completes the GNRC IPv6 refactor. Congratz 🎉 GO |
Thank you @jia200x for all the review work for this project! |
no problem! thanks for all the work :) |
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
I had this idea when implementing RIOT-OS#10382 and RIOT-OS#10392 as I introduced a very similar structure to python's standard unittests in those and it could also reduce some code duplication between those two tests.
Contribution description
This introduces a dedicated test application for GNRC's RPL source router header implementation. It utilizes
scapy
for the generation of the routing headers. It also moves the unittests from the unittests application into this application.Testing procedure
Compile
tests/gnrc_rpl_srh
and flash it to a board of your choice. Usesudo make test
to run (due to the required Ethernet frame construction with the tap interface you need root permissions). The tests might hang and fail due toscapy
's sniffer sometimes not picking up the expected packet. Maybe someone can help me with syncing the main thread and the sniffer thread of the python script here?Issues/PRs references
Depends on #10242, #10244, and
#10300(merged) and their dependencies:Addresses #8941 partly.