OpenThread released by Nest is tested by a number of tools.
CI performs the following tests on the OpenThread repository:
- Build checks
- Build all example platforms using the GNU Arm Embedded Toolchain
arm-gcc, across versions 4.9, 5.4, 6)
- Build the simulator platform (POSIX) using GCC and Clang
- (a) and (b) for all example applications
- (a) and (b) for both Full Thread Device (FTD) and Minimal Thread Device (MTD) configurations
- (a) and (b) for both System-on-Chip (SoC) and Network Co-Processor (NCP) configurations
- Build all example platforms using the GNU Arm Embedded Toolchain (
- Static analysis, using Clang Static Analyzer
- Code style checks
- Unit tests
- Functional tests
OpenThread is fuzz tested with OSS-Fuzz. In this testing technique, invalid and random inputs are submitted at a high frequency and volume to software in order to find issues such as memory leaks or crashes.
See the OpenThread repository for the current fuzzing build targets.
Use the following tools to test your own OpenThread product.
Wireshark is an open-source network protocol analyzer for traffic running on physical and virtual network interfaces. The Thread protocol is supported in Wireshark 2.4.0 and later. Documentation and downloads for this tool can be found at wireshark.org.
Pyspinel is a Python CLI for the Spinel protocol, used to configure and manage OpenThread NCPs. This CLI is primarily targeted to CI tests, but can be used manually to experiment with and test OpenThread NCP instances.
Pyspinel is used:
- to add simulated NCP testing to continuous integration
- to automate testing of testbeds running NCP firmware on hardware
- to debug NCP builds of OpenThread
For more information, see the
in the Pyspinel repository.
Pyspinel comes with a sniffer tool that turns a Spinel NCP node into a promiscuous packet sniffer. This tool intializes a device into sniffer mode and outputs a pcap stream that can be saved or piped directly into Wireshark.
For more information on how to use the sniffer, see the
README in the