Project testing
OpenThread released by Google is tested by a number of tools.
Continuous integration
OpenThread uses Travis CI and AppVeyor for continuous integration (CI), and Codecov for code coverage.
CI performs build checks for all example platforms using the GNU Arm Embedded Toolchain and for the POSIX platform using GCC, Clang, and Android. It also builds and tests against x86, platform architecture, and Thread device configurations. For more information on specific build targets, see the OpenThread Travis build matrix.
In addition, CI performs:
- Code style checks
using
clang-format - Unit tests
- Functional
tests
against CLI,
wpantund(withtoranj), and Pyspinel
OSS-Fuzz
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.
Product testing
Use the following tools to test your own OpenThread product.
Wireshark
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.
For more information on how Thread is supported in Wireshark, see Packet sniffing with Pyspinel.
Pyspinel
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
README
in the Pyspinel repository.