TL;DR: Is there a way to clue in mbed test --unittests that there are unit tests outside of the mbed-os directory? Because I don’t want to put my own (non-OS-related) code in there. I’m writing a bit of code that may eventually become a library, but the only really straightforward way to even begin…

Personally, I use TDD with Google Test and gMock. I use CMake to set them up and run them, I don’t use the mbed-cli at all for that. In the past I tried copying the mbed unit tests to my project, removing all the tests and using only mine but it was tool complicated to integrate in the mbed workflo…

Was also my question here , but unfortunately it does not seem to be possible. The recent CMake integration does not support this use case yet. Use an external build tool such as CMake to include the available stubs in the UNITTESTS directory and try building on that. @ladislas , I’m also working on …

[image] boraozgen: @ladislas , I’m also working on setting up a unit test system for my code. I looked into Google Mock but as far as I’ve seen it isn’t really suitable for “C-style” C++ code, where the dependencies are not implementations of abstract classes, which is usually the case in Mbed. …

If you haven’t read it yet, I recommend Test Driven Development for Embedded C, a real page turner (no kidding) – the guy uses CppUTest/CppUMock. Just finished reading that one :smile: Wonderful book indeed. I found the documentation less clear than Google Test which works great with CMake. T…

[image] boraozgen: Adding wrappers just for testing feels like a lot of hassle for me. Are there other benefits of using this approach? For us it makes dependency injection much easier (we will try boost::DI in the future) and allows for a clear abstraction that we decide. Again, we don’t do…

it might be a bit artificial but the separation of concerns this way makes TDD and unit testing easier for the team. but I’m not saying it’s the only way. for the LCD stuff, we also use google mock for “specification” – we know that the DSI command must be called 101 times for the LCD to work corre…

Hi @ladislas , @boraozgen , I’ve been reading this thread and I’ve found it very interesting. Beyond the framework, I have been wondering about some things. As @ladislas said, low-level stubs can be very interesting when you want to test new peripherals or libraries which work against mbed OS driv…

I have opened a new thread: [image] High Level Mbed OS testing Best practice Hi everyone, I am working with Mbed OS to develop high-level applications and high-level libraries. Some of my libraries depends on the Mbed OS Connectivity API. I wanted to implement Test in or…

Hi @ladislas @boraozgen , I don’t know if you are already working with out-of-tree unit testing over Mbed OS 6, but I have just configured an example project which runs unit tests using mbed stubs and fakes but without including it in Mbed OS folder. This allows me to include tests in each library w…

can you share the project? :slight_smile:

Run unit tests for MY code

Mbed OS

davidAlonso (David Alonso) June 16, 2021, 11:20am 9

I have opened a new thread:

Topic		Replies	Views
High Level Mbed OS testing Best practice mbed_os , greentea	12	1333	June 21, 2021
Out-of-tree unit testing Mbed OS	3	490	October 9, 2020
Mbed 6.15 unit test Mbed OS	0	216	March 15, 2022
Unit Testing With Mbed 6 Mbed OS	0	451	August 11, 2022
Unit testing framework Mbed OS	1	1529	December 1, 2015

Run unit tests for MY code

Related topics