This test needs the pool size for limit objects set to 3 by default so
it does not fail. As this is done with the 'app.config' file, we
explicitly disable Kconfig by default.
chronos is indirectly blacklisted because of missing periph_uart feature.
hamilton doesn't provide periph_uart when stdio_rtt is disabled (because
of ethos dependency to stdio_uart) and ruuvitag/thingy52 provide the
periph_uart feature so stdio_uart can work on these boards.
Using the shell to run unittests allows not needing
to wait for a string at the start of the test which
makes the test independent having the application reset
after the terminal is open. The same goes for triggering
sending UDP test pkts.
- Define test_utils_interactive_sync as DEFAULT_MODULE in Makefile.tests_common
- For tests disabling autoinit, add test_utils_interactive_sync to main
- Add DISABLE_MODULE += test_utils_interactive_sync for tests requiring
sudo, `tests/shell`, `tests/minimal` and `tests/stdin`
- Add shell_commands to tests/periph_wdt and tests/struct_tm_utility to
pull `r` and `s` commands
- Remove includes and usage in `tests/main.c` for tests that where
already using test_utils_interactive_sync
- Since `printf()` is buffered it might not arrive in a single
read to pexpect. Regex which terminate in a group match might
match only some elements, this might break tests that depend
on exact group matching.
Previously `ifconfig` would only know link-local addresses
(printed as 'local') and everything else would be 'global'.
This is wrong for site-local and unique local addresses which were
also denoted as global.
So use the already existing helper functions to determine the correct
type of IPv6 address when printing.
Adds a test case for when the following conditions cause a crash:
- a subsequent fragment is received before the first
- the reassembly buffer is currently filled up when another fragment of
a different datagram arrives and thus needs to be cached out to make
room for the new reassembly
While looking at tests/gnrc_ipv6_ext_frag again while writing
RIOT-OS/Release-Specs#137, I noticed that several of tests that I
definitely wrote myself from scretch are attributed wrong (and
sometimes even documented wrong). I guess this was caused by just
copy-pasting the files...
