Unity Test API VS greatest

Here is the github repo link of Unity: https://github.com/ThrowTheSwitch/Unity

You shouldn't need a configuration file to write tests with Unity. You are using Unity from Unity on Github right? You can use YAML files to along with some helper scripts Unity and related tools provide, but it doesn't sound like you are there yet.

First, for context, as part of my internship, I'm writing unit tests for functions from a hardware manufacturer provided C++ library. This particular code is testing if the relevant function returns a unique location ID for each hardware device. The test assert macro I'm using is from the Unity test framework C library.

I use Unity Fixtues + FFF + CException framework.

Edit: I also tried Googling "list of Unity test framework macros" and found this, which is kind of helpful, but still doesn't actually explain how the correct syntax for specific macros or precisely what they do. I guess basically, I'm looking for something similar to the entries on cppreference.com, but for the Unity macros instead of the standard library functions for C++.

I know Unity is used in the embedded industry, I also use it for my own personal projects. It’s great and does everything I need.

If you're using the ESP-IDF framework, it already comes with Unity. It's easy to use, and you have the Test Driven Development for Embedded C book as reference.

I use the Unity Test Framework: https://github.com/ThrowTheSwitch/Unity

Drawing a comparison to heavyweights like Google Test isn't fair game though. Your real competition is the likes of Unity and CuTest. My question to you, what does Muon have that Unity doesn't? What's the selling point to get me to switch over?

I’ve only used greatest.h before. It was pretty ok, easy enough to use.

Get a unit test library/framework. There are many good ones, but if you can't decide take greatest because it's a single-header library and easy to use.

Greatest is 1 header file. https://github.com/silentbicycle/greatest

I'd recommend writing tests. Use a testing library (e.g. Unity or Greatest). Even if that sounds like more work right now, it can help find issues early, gives you confidence that your code does what it should, and often lets you progress much faster.

I have used Greatest. Works great for my purposes.

I use greatest it's pretty easy and just a header to copy into the source tree.

(TL;DR greatest is the greatest test framework I could find for that particular use case. See my "research I did" link for details.)