But when working with embedded devices we software developers usually need to deal with hardware dependencies. Hardware dependencies? When dealing with hardware dependencies we typically see one of the following:
- skip unit testing altogether - it is just too damn hard (not any more…)
- use a mock framework
We use mocks to replace hardware dependencies with code. Often the hardware is not yet ready or we want to test on an environment where is not available (like for example continuous integration).
Mocking out hardware dependency makes writing unit-tests much easier. We focus on testing the code of our embedded application using the interface of the hardware dependency.
Sure, we need to test our code with the real hardware dependency. But this is not unit-testing - this is integration-testing.
Enough said, lets look into some code!
The simplest embedded code sample cmp_demo.c:
The interface of the hardware dependency dep_demo.h:
And the unit test test_cmp_demo.c:
Our test includes mocks/mock_dep_demo.h and we tell the mock how it should behave “dep_init_ExpectAndReturn(42, 420);”.
To make this work all we need to do is to tell the build system to create the mock based on the interface. Just add this to CMakeLists.txt:
I left out some details for brevity. Here you can find the complete sample code including CMock source and build files.
I opened a ticket with Espressif and I hope that they will include CMock in the standard ESP-IDF release.
I hope this post is helpful to you.
All the best, Mark