Embedded Artistry was founded with the goal of creating reliable, safe, and well-tested embedded systems. The sad fact is that most embedded software that we've encountered is low-quality and untested. Perhaps this holds true for most of the software industry - the continual procession of hacks, flaws, and errors is discouraging.
We are focused on ways that we can all improve at our craft. Testing our systems, especially in an automated way, is a direct approach at identifying bugs early and improving our software quality.
We decided to make our list of testing resources publicly available. If you have any favorites which aren't listed here, leave us a comment!
Table of Contents:
- Unit testing
- Debugger-based testing using metal.test
- Phil Koopman's lectures on embedded software quality and testing
Most developers know they should be writing unit tests as they develop new features. If you're unfamiliar with the concept, unit testing focuses on testing the finest granularity of our software, the functions and modules, in an independent and automated manner. We want to ensure that the small pieces operate correctly before we combine them into larger cooperating modules. By testing at the finest granularity, we reduce the total number of test combinations that are needed to cover all possible logic states. By testing in an automated manner, we can ensure that any changes we make don't introduce unintended errors.
"A key advantage of well tested code is the ability to perform random acts of kindness to it. Tending to your code like a garden. Small improvements add up and compound. Without tests, it's hard to be confident in even seemingly inconsequential changes." -Antonio Cangiano (@acangiano)
Unfortunately, at Embedded Artistry we’ve only worked on a handful of projects that perform unit testing. The primary reason for this is that many developers simply don’t know where to start when it comes to writing unit tests for embedded systems. The task feels so daunting and the schedule pressures are so strong that they tend to avoid unit testing all together.
James Grenning and TDD
James Grenning has put a tremendous amount of effort into teaching embedded systems developers how to adopt TDD. He published an embedded systems classic, _Test-Driven Development for Embedded C_, and regularly conducts TDD training seminars .
James has written extensively about TDD on his blog . Here are some of our favorite posts:
- TDD Guided by ZOMBIES
- walks through testing a circular buffer
- Physics of Test Driven Development
- Manual Test is Unsustainable
- I've got integration and system tests, why do I need unit tests?
- Preventing Brittle Tests
You can also watch these talks for an introduction into the how and why of TDD:
- Webinar - Test-Driven Development for Embedded Software
- NDC conference talk: Test Driven Development in C/C++
If you're interested in taking a training class, you can learn more on James's website.
Matt Chernosky and Electron Vector
Matt Chernosky, who runs the Electron Vector blog, is an invaluable resource for embedded unit testing and TDD. If you are having a hard time getting started with unit testing and TDD, Matt's articles provide a straightforward and accessible approach.
Here are some of our favorite articles from Matt's blog:
- 7 tips for adding unit tests to existing firmware
- Mocking hardware interfaces using Ceedling and CMock
- Practice writing code without the hardware
- When you want to unit test, create well-defined software units
- When you want to unit test, abstract the hardware
- Event-based interfaces for testability
- Avoiding mocks by enqueueing events
- Test-driving with mocks instead of hardware
Throw the Switch
Aside from creating testing tools, Throw the Switch maintains a library of test-related articles and a course called Unit Testing & Other Embedded Software Catalysts . Additional courses related to unit testing for embedded systems are being developed.
Unit Testing Frameworks
Listed below are frequently recommended unit testing frameworks for C and C++. There are more unit testing frameworks in existence than we can ever review, so again this list is not exhaustive. If nothing jumps out at you in this list, keep looking to find one that fits your team’s development style.
Cmocka is the C unit testing framework we started with. Cmocka ships with built-in mock object support and operates similarly to Unity & CMock. The framework is built with C standard library functions and works well for embedded systems testing.
Catch appears to be the most popular C++ unit testing framework. Catch is a header-only library which supports C++11, C++14, and C++17.
Doctest is the unit test framework we use for EA’s C++ embedded framework project. Doctest is similar to Catch and is also header-only. Our favorite attribute of Doctest is that it keeps the test code alongside the implementation code. Doctest also enables you to write tests in headers, which Catch does not support.
GoogleTest is Google's C++ unit testing framework. GoogleTest is one of the few C++ frameworks with built-in mocking support.
CppUTest is a C++ test suite that was designed with embedded developers in mind. This framework is featured in James Grenning's book _ Test-Driven Development for Embedded C _. C++ features within the framework are kept to a minimum enabling it to be used for both C and C++ unit testing. CppUTest has built-in support for mocking.
If you're interested in mock object support for C++, check out GoogleMock , Trompeloeil , and FakeIt . Each of these mocking frameworks can be integrated with the unit test frameworks mentioned above.
If you're brand-new to TDD, read through this walkthrough to get a sense of the approach:
Steve Branam, who writes at Flink and Blink , has written a few posts on testing:
- Testing is how you avoid looking stupid
- Off-Target Testing and TDD for Embedded Systems
- Review: Test Driven Development for Embedded C, James W. Grenning
Steve recommended Jeff Langr's Modern C++ Programming with Test-Driven Development: Code Better, Sleep Better as another resource for embedded C++ developers.
Embedded Debugger-Based Testing
We always want to run as many tests as possible on a host PC when unit testing embedded systems code. However, we can’t test every aspect of our system on a host machine. Before shipping the final system, we need to evaluate the target compiler, issues which only present themselves on the target (e.g. endianness, timing), and the actual target hardware and hardware interfaces.
is a framework which can help us with on-target testing. This project is maintained by Klemens Morgenstern, an independent contractor and consultant. Metal.test enables automated execution of remote code using debugger hardware, such as J-LINK or ST-Link. The project currently supports
lldb support is planned for a future release.
- I/O Forwarding
- Code Coverage
- Unit testing
- Call tracing
- Function Stubbing at link-time
- Extensive documentation (in the GitHub repository Wiki )
Metal.test also includes a plugin system. While it's not essential, plugin support enables developers to extend the functionality to support any use case that a debugger can support.
Klemens is looking for feedback on metal.test . Don't hesitate to reach out with questions, issues, or other feedback.
Phil Koopman on Testing and Software Quality
Phil has produced an immense and invaluable body of work, much of it focused on embedded software quality. The lecture notes for his embedded systems courses are available online, and he regularly posts lecture videos on his Youtube channel .
Here's a selection of his lectures that are related to testing and software quality:
- Embedded Software Quality: Why is it so terrible? What can we do about it?
- Unit Testing
- Integration Testing
- Testing Quality
- System Level Testing
- SQA isn't testing
Did We Miss Anything?
If you have a testing resource that you love, leave us a comment below and we will add it to the list!