MaRC's existing unit tests follow a simple pattern where the boolean result of all test cases in a given unit test program are combined into a single overall pass/fail result. That is fine for automated test runs, but it isn't ideal for debugging purposes since more work is needed to pinpoint exactly which test case in a given unit test program has failed.
Leverage the Boost.Test framework to improve MaRC's unit tests.
MaRC's existing unit tests follow a simple pattern where the boolean result of all test cases in a given unit test program are combined into a single overall pass/fail result. That is fine for automated test runs, but it isn't ideal for debugging purposes since more work is needed to pinpoint exactly which test case in a given unit test program has failed.
Leverage the Boost.Test framework to improve MaRC's unit tests.