Create if_lib package containing all the modules and adapt the *.py files
to import each other using the intra-package references.
The idea behind a package is to invoke test.py either by permanently
modifying PYTHONPATH in user profile via adding path to $RIOTBASE/dist/tests
or make temporary PYTHONPATH changes during the invocation:
PYTHONPATH=$PYTHONPATH:$RIOTBASE/dist/tests python3 test.py
Leave periph_i2c_if.py in the same folder as test.py as this file is
just a Python wrapper around periph specific main.c.
Update BPT memory map. Use definitions generated with the latest code
generator. Both routine names and mapping have changed.
Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
The `test_ipv6_group_join__ENOMEM()` tests joining multicast groups,
so we need to iterate `GNRC_NETIF_IPV6_GROUPS_NUMOF` times to fill up
all addresses, not `GNRC_NETIF_IPV6_ADDRS_NUMOF`.
Use a minimalistic dummy instead of the default interface for testing
the `gnrc_ipv6_ext` module.
Currently the default interface is used which leads to problems with
this test, since random traffic on the medium or a missing default
interface might lead to failed results.
Since the `tap` dependency is removed for `native`, I add this test for
testing on CI.
Use a minimalistic dummy instead of the default interface for testing
the `gnrc_sixlowpan` module
Currently the default interface is used which leads to problems with
this test, since random traffic on the medium might lead to failed
results.
PR #9585 changed the output for the dump slightly, so now this test
is failing. This fixes that and should also fix some issues from the
2017.07 release tests.
Add automated script to test devices against a known testers.
This will make it easier to run tests instead of manual testing.
This is something that works for now but will be better integrated later.
`UINT16_MAX` should be the same value on all platforms, so why not use
`puts` instead of `printf` here instead. Also, `llvm` detects an issue
with using the `UINT16_MAX` macro with `PRIu16` here.
This is an effort to automate UART testing using the same framework as
was already introduced for i2c. The framework relies on shell commands
to return invocation status and data in a special way:
1. Invocation status: Success or Error
2. Data inside the []
Hence this patch adds invocation status to the UART init command and
invocation status and data to the printer.
Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
