Unity Test API VS benchmark

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'm aware of one by Google that I used a couple times, but IMO it's better to capture real runtime data from a fully-operational process than to carve out the benchmarkable bits and test them in isolation, so I track information during program testing and print it all to a log instead of using things like that.

If you just want to do some quick benchmarks, you can just use std::chrono::high_resolution_clock::now(). Call it before the code that you are benchmarking and then immediately after. Take them away and you have your duration. If you want to use a proper benchmarking tool then I can totally recommend Google Benchmark. Fantastic benchmarking tool. Honourable mention would be Quick Bench which is an online tool that uses Google Benchmark.

I tried to install google benchmark(https://github.com/google/benchmark) in my ubuntu machine by :

We don't know if it's a lie until we verify it and that's not difficult, you have a quicksort implementation in a couple of languages, you'll need to pass the necessary parameters to show the time needed by a function call to execute to the compiler or interpreter or you may use use a library(like benchmark for C++) and you're good to go.

If you are uncertain about the performance characteristics of a function you should ALWAYS benchmark it. Googles Benchmark library is wonderful for quick micro benchmarks. For more complex things, perhaps look into profiling and then look at invocation counts of copy constructors.

Your compiler may be optimising away your loop, there. I typically use a micro-benchmarking tool for these types of tests. You could try Google Benchmark. It’s available in most OS’ package managers, but pretty easy to build from source if not

C++: C++ has quite a number of benchmarking libraries some of the recent ones involving C++ 20's flexibility. The most notable being Google Bench and UT. C does not have many specific benchmarking libraries, but you can easily integrate C code with C++ benchmarking libraries in order to test the performance of your C code.