Criterion VS utest.h

I really like Google Test, but am planning on doing some embedded development in C, where I sometimes find it awkward to test C code using a C++ library.

Therefore, I wrote a small unit test library closely mimicking Google Test. It consists of two source files, "rktest.c" and "rktest.h", and is about 1k lines of code and written in C99.

It uses a trick for self registering tests by placing pointers to the unit test functions into a known place in program memory, that I first learned about from https://github.com/christophercrouzet/rexo/ and https://github.com/Snaipe/Criterion/.

I have been using criterion on a recent project and enjoying it.

My school uses Criterion (doc). source code

Otherwise I use criterion https://github.com/Snaipe/Criterion, since a few cases can't be checked properly in python (or are a hassle to do)

Try this link for setup in doc.

https://github.com/Snaipe/Criterion < - repository for the unit-testing library.

I would say simple things are simple. CMake does use RPATH on RPATH compatible platforms, there is no need to copy DLLs. In fact, if the DLL depends on assets relative ot its location now you are just digging a deep hole for yourself for no good reason. On platforms where RPATH is not supported (Windows), you should make DLLs available via PATH, which Just Works tm. This is a shortcoming of Windows. You are free to forward your complaints to Microsoft. Regardless, here's some help with the PATH thing.

This fork of it has proper CMake integration and provides a module for automatic test discovery with the unique ability to handle DLL finding for you on Windows, which is documented here.