fff VS goos-code-examples

Only cool framework in my opinion. I wish I had the guts to delve so deeply into Variadic Macros.

You can use GoogleTests. Also, if you have C functions which need to be mocked, you can try using the FFF framework along with with gtest.

I use Unity Fixtues + FFF + CException framework.

For news reading, surely, I'd go with newsboat, perfect for this. Newsboat also fetches Odysee and Youtube channels, and you can integrate mpv to it to watch the videos. No ads, nothing. For file manager, I'm using fff, very minimal and relatively easy to configure.

Also recommend checking out fff.

FFF Github page

Everything else was covered: Ceedling+Unity+CMock for Unit Testing in C, CppuTest or GoogleTest or other options for C/C++. FFF is also useful when mocking. If you test and develop your modules correctly, they should when they are in your application. If you are developing using an Event-Driven Framework like QP or QML, then I would not test anything to do with the framework, but the functions that are called in each event. Same thing if you are using an RTOS, test what's inside your threads/tasks.

Here is link number 1 - Previous text "fff"

Interesting! Always nice to see more of these kind of test tools for C. I'm currently using fff and Unity

A very good way to use mocks (not like illustrated here) is explained in the GOOS book by Freeman and Pryce: http://www.growing-object-oriented-software.com/

Further read: Growing Object Oriented Software

On the subject of TDD, the way I've done TDD has been very similar to the technique described in the article. Work in very small increments, try to get a very thin vertical slice of functionality working through the system as soon as possible and, whatever you build, try to get it working end-to-end as soon as you can. Of course, I use tests to drive the work but I find it very helpful to use tests to drive those thin vertical slices of functionality.

The book that really helped me to start working in this way is Growing Object Oriented Software, Guided by Tests by Steve Freeman and Nat Pryce [0]. The book has been around for a few years at this point and tech has moved on since then, as have some of the techniques, but it's still a very interesting read. (Disclosure: I was lucky enough to briefly work with one of the authors a few years ago but I was a fan of the book long before then.)

[0] http://www.growing-object-oriented-software.com/

I think this is still the most referenced work. You probably know that one like the back of your hand, but it's still good to reference in general to convey confidence in the topic.

[3] Have a look at the testing asynchronous systems examples in the GOOS Code examples repository for a more object-oriented implementation of helper for the polling for changes strategy, and also examples of the capturing notifications strategy.