OrderManager VS Catch

https://github.com/Diffeomorph/OrderManager/ Here is my project in full. I am having problems making the testing work. This is made worse by the lack of good examples and documentation online on Boost testing.

Rate my c++ code out of 10 currently. https://github.com/Diffeomorph/OrderManager. I think the naming of variables and functions needs to be more consistent.

Another possible issue would be the include(Catch) in your root cmakelists.txt . To include Catch there it must be part of your module path. Otherwise you have to include the path to that catch2 cmake file. Here is that file in their repository - https://github.com/catchorg/Catch2/blob/devel/extras/Catch.cmake . I recon that CMake doesn't know about this file since you call find_package(Catch2 REQUIRED) later in your subdirectory

Unit test coverage by Catch2 framework.

Looks good but currently at least REQUIRE (most likely all the other checks too but I didn't test that) fails to correctly evaluate some expressions, due to fundamental problems with macros. One example is described in this issue of the Catch2 repository.

However, you can use a unit test framework like GoogleTest or Catch2 whic creates a main() function for you which allows you to run single functions, as long as they have been created through some preprocessor macros. Then you can use a VS Code test adapter like this or this which may let you run a single test by right clicking it directly in VS Code.

include(FetchContent) FetchContent_Declare( Catch2 GIT_REPOSITORY https://github.com/catchorg/Catch2.git GIT_TAG v3.0.0-preview4 ) FetchContent_Declare( fmt GIT_REPOSITORY https://github.com/fmtlib/fmt.git GIT_TAG 9.1.0 ) FetchContent_Declare( scnlib GIT_REPOSITORY https://github.com/eliaskosunen/scnlib.git GIT_TAG v1.1.2 ) FetchContent_MakeAvailable(Catch2 fmt scnlib)

Make sure you write unit tests, I use gtest but catch2 is also good.

I've only ever personally used Catch2, Boost.Test, and a few proprietary unit test frameworks from my company. I enjoy using both Catch2 and Boost.Test, but they have a very different feel. Of these two I find Catch2 easier to get started with. It also has very good CMake an CTest integration. I have heard good things about GoogleTest, but I have never used it myself. GoogleTest also has good CTest support

Writing unit tests for my static site generator - palpatine, taught me an entirely new testing framework called Catch2. For my Hacktoberfest pull request this year I had done a unit testing contribution for a repository and I am currently working on building a microservice for my cloud computing class which requires us to use Jest for JavaScript unit testing. So, I can say that I have some experience with unit testing and continuing to develop my skills in it.

To set up the GitHub Actions, we first need to create 2 folders, a .github in the root directory of the repository, and a workflows folder inside .github folder we just created. In the workflows folder, we create a YAML file to save the GitHub Actions configuration. I programmed my project in C++ with Catch 2 for the testing framework， my GitHub Actions should be set up with C++ software stacks. The process of how I set up my YAML is as follows:

This week, I added a testing module to my SSG. Since my SSG was created using C++, I used Catch2 as my testing framework. I chose Catch2 as my testing framework since it seemed to be the most popular among C++ developers, and it was all contained within a single header file.