CppUTest VS Catch

# Use the Debian base image as our starting point. FROM debian:bullseye # Install the required packages. RUN apt update -y && \ apt -y install g++=4:10.2.1-1 \ cmake=3.18.4-2+deb11u1 \ libtool=2.4.6-15 \ autoconf=2.69-14 \ git=1:2.30.2-1+deb11u2 \ gdb=10.1-1.7 \ wget=1.21-1+deb11u1 \ bzip2=1.0.8-4 \ make=4.3-4.1 \ stlink-tools=1.6.1+ds-3 # Clone and install CppUTest RUN git clone https://github.com/cpputest/cpputest WORKDIR /cpputest RUN autoreconf . -i && \ ./configure && \ make tdd ENV CPPUTEST_HOME=/cpputest # Set the working directory for your project WORKDIR /work # Download and set up the GNU Arm toolchain RUN wget https://developer.arm.com/-/media/Files/downloads/gnu-rm/10.3-2021.10/gcc-arm-none-eabi-10.3-2021.10-x86_64-linux.tar.bz2 && \ tar -xjf gcc-arm-none-eabi-10.3-2021.10-x86_64-linux.tar.bz2 && \ rm gcc-arm-none-eabi-10.3-2021.10-x86_64-linux.tar.bz2 && \ mv gcc-arm-none-eabi-10.3-2021.10 /opt/gcc-arm ENV PATH="/opt/gcc-arm/bin:${PATH}"

The C++ testing framework Catch2 enables this kind of testing. The first time I saw it I couldn't figure out how some of the tests would even pass.

It turns out that using some evil macro magic, each test re-runs from the start for each inner section [1]. It also makes deduplicating setup code completely painless and natural.

You just have to get over the completely non-standard control flow. It's a good standard bearer for why metaprogramming is great, even if you're forced to do it in C/C++'s awful macro system.

[1] https://github.com/catchorg/Catch2/blob/devel/docs/tutorial....

Identification: Use tools like pytest-rerunfailures, TestNg, and Catch2 to automatically rerun failed tests.

This is one area where a BDD style framework like catch2[0] really shines, IMO. The way tests are written in this style naturally lends itself to self-documenting each branch

[0]: https://github.com/catchorg/Catch2

The code uses catch2 to test for correctness and performance. Catch2 is a unit testing framework for C++, but it also provides basic micro-benchmarking features. Unfortunately, it doesn't provide any way to visualise the results, so I created a script and submitted PR adding plotting capabilities to Catch.

https://github.com/catchorg/Catch2 (for unit testing, need to do timing yourself)

```c++ // https://github.com/catchorg/Catch2/tree/Catch1.x // https://github.com/philsquared/Catch/releases/download/v1.12.2/catch.hpp

Include(FetchContent) FetchContent_Declare(Catch2 GIT_REPOSITORY https://github.com/catchorg/Catch2.git GIT_TAG v3.3.2 ) FetchContent_MakeAvailable(Catch2)