OrderManager VS Google Test

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.

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.

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

load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive") BAZEL_TOOLCHAIN_TAG = "0.7.2" BAZEL_TOOLCHAIN_SHA = "f7aa8e59c9d3cafde6edb372d9bd25fb4ee7293ab20b916d867cd0baaa642529" http_archive( name = "com_grail_bazel_toolchain", sha256 = BAZEL_TOOLCHAIN_SHA, strip_prefix = "bazel-toolchain-{tag}".format(tag = BAZEL_TOOLCHAIN_TAG), canonical_id = BAZEL_TOOLCHAIN_TAG, url = "https://github.com/grailbio/bazel-toolchain/archive/{tag}.tar.gz".format(tag = BAZEL_TOOLCHAIN_TAG), ) load("@com_grail_bazel_toolchain//toolchain:deps.bzl", "bazel_toolchain_dependencies") bazel_toolchain_dependencies() load("@com_grail_bazel_toolchain//toolchain:rules.bzl", "llvm_toolchain") llvm_toolchain( name = "llvm_toolchain", llvm_version = "15.0.5", ) load("@llvm_toolchain//:toolchains.bzl", "llvm_register_toolchains") llvm_register_toolchains() http_archive( name = "com_google_googletest", urls = ["https://github.com/google/googletest/archive/609281088cfefc76f9d0ce82e1ff6c30cc3591e5.zip"], strip_prefix = "googletest-609281088cfefc76f9d0ce82e1ff6c30cc3591e5", )

> Your test suite may not be able to hit it either.

Minor nitpick, process terminations are unit-testable in general; see e.g. https://github.com/google/googletest/blob/main/docs/advanced...

include(FetchContent) FetchContent_Declare( googletest GIT_REPOSITORY https://github.com/google/googletest.git GIT_TAG release-1.12.1 ) add_executable(tests main_tests.cpp) target_link_libraries(tests GTest::gtest_main) include(GoogleTest) gtest_discover_tests(tests)

git clone https://github.com/google/googletest.git # Dowload the Google Test repository cd googletest # Main directory of the cloned repository. mkdir -p build # Create a directory to hold the build output. cd build # Move

Swap Boost Test for something better and more modern. The current industry standard is Catch2 and google test. There are much better documentation available on how to use those than the ancient and dying boost stuff.

To ensure the quality of our iOS Apps during development and testing, we decide to use Jenkins jobs to test it on WeTest cloud devices for every update of our app. After investigating various tools, we use gtest + gmock as the unit test framework and Appium as the UI test framework for the SDK.

I'm keen to do some of the exercises outlined here; however, before I begin, I've been trying to set up C unit tests for any code that I eventually write. In the past, I've used GoogleTest and CMake in my own C projects, which is pretty straightforward to set up but I haven't been able to get this combo to work for the OS161 kernel so far.

git clone https://github.com/google/googletest.git # Dowload the Google Test repository cd googletest # Main directory of the cloned repository. mkdir -p build # Create a directory to hold the build output. cd build # Move into the build directory. cmake .. # Generate native build scripts for GoogleTest. make # Compile sudo make install # Install in /usr/local/ by default