RIOT/tests/lwip_sock_udp
Marian Buschsieweke eb1279005c
tests: Cleanup access to internal variables
Replace direct accesses to sched_active_thread and sched_active_pid with
the helper functions thread_getpid() and thread_get_active(). This serves
two purposes:

1. It makes accidental writes to those variable from outside core less likely.
2. Casting off the volatile qualifier is now well contained to those two
   functions
2020-08-24 09:08:01 +02:00
..
2019-11-27 14:12:12 +01:00
2018-06-11 19:12:02 +02:00

Tests for lwIP's sock_udp port

This tests the sock_udp port of lwIP. There is no network device needed since a virtual device is provided at the backend.

These tests test both IPv4 and IPv6 capabilities. They can be activated by the LWIP_IPV4 and LWIP_IPV6 environment variables to a non-zero value. IPv6 is activated by default:

make all test
# or
LWIP_IPV6=1 make all test

To just test IPv4 set the LWIP_IPV4 to a non-zero value (IPv6 will be deactivated automatically):

LWIP_IPV4=1 make all test

To test both set the LWIP_IPV4 and LWIP_IPV6 to a non-zero value:

LWIP_IPV4=1 LWIP_IPV6=1 make all test

Since lwIP uses a lot of macro magic to activate/deactivate these capabilities it is advisable to test all three configurations individually (just IPv4, just IPv6, IPv4/IPv6 dual stack mode).