We can use Docker to set up a stable and repeatable environment where our firmware is built and unit tested. Furthermore, we can use access the hardware from the container to perform integration testing. A shared directory will allow us to access our code from within the containerized environment.

from https://dev.to/djangostars/what-is-docker-and-how-to-use-it-with-python-tutorial-87a:

* 1 application = 1 container. * Run the process in the foreground (don't use systemd, upstart or any other similar tools). * Keep data out of containers – use volumes. * Do not use SSH (if you need to step into container, you can use the docker exec command). * Avoid manual configurations (or actions) inside container.

Check

http://embunit.sourceforge.net/

http://programmers.stackexchange.com/questions/104332/best-practice-when-unit-testing-for-embedded-development

https://dmitryfrank.com/articles/unit_testing_embedded_c_applications

http://eradman.com/posts/tdd-in-c.html

framekworks:

• seatest
• MinUnit
• Unity
• https://github.com/bvdberg/ctest

https://wiki.jenkins.io/display/JENKINS/Test+Results+Analyzer+Plugin