This post was originally published on Mbed Developer Blog.
Mbed OS now runs on over 150 development boards, and had over 3,000 commits last year alone. To keep the operating system stable when developing at such a high pace, we invested in automated testing: We now have test farms in two locations with over 1,000 real development boards, 1,150 functional tests, and roughly 40,000 hours of testing on physical hardware for every major release. Feel inspired? All tools to build and run the tests are open source, and in this blog post we’ll show you where to find information on how to get started building tests for your own applications.
Greentea is our testing tool that automates the process of flashing development boards, starting tests, and collecting test results into test reports. Mbed OS tests are written in Unity, an open source unit testing library. In addition, Greentea supports ‘host tests’. These are Python scripts that run on a computer and can communicate with the device being tested. You can, for example, verify that a value was actually written to the cloud when the device said it did so.
To get started building tests, either watch the video above or head over to the documentation. We have additional tutorials on:
In addition, you can find an example application that uses host tests to verify that data was actually sent from a device to the cloud here: mbed-http-integration-test.
Jan Jongboom is a Developer Evangelist for the Internet of Things at Arm, and the author of the Mbed HTTP library (now with tests!).