During development, I tend to add scratch functions to test a particular part of the code. In this video, I try to handle these functions in a less ugly way.

0:00 Background
1:20 Move the test functions
2:50 Add TEST argument to make
5:15 Fix errors
5:45 Suppress unused functions
7:02 Ugly workaround
7:50 Build all functions in CI
9:53 git commit
11:00 Last words

#embeddedsystems  #cprogramming 

Code: https://github.com/artfulbytes/nsumo_video

⌨️ My development environment
https://www.artfulbytes.com/devenv

🌍 Links
GitHub - https://github.com/artfulbytes
Website - https://www.artfulbytes.com

👨‍💻 About me
Hi and welcome. I'm Niklas, an embedded systems engineer from Sweden. On this channel, I make practical videos about embedded systems or, in general terms, about building and programming hardware.

Artful Bytes

A developer improves their embedded systems project's test function handling by moving test functions to a separate file and creating a build system that accepts test function names as arguments. The solution includes makefile modifications to switch between main and test builds, automatic test function discovery using regex, and CI integration to build all tests automatically.

My Small Test Functions | Embedded System Project Series #15