You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, threads are only used for testing framework (and not testing cases themselves). IMO, it's better to shift responsibility for running tests in parallel to the testing environment (make test -j8) and decouple it from the testing code.
I would also prefer a simple solution that doesn't require Threads. I've written a small unit test framework for CAF. With minor modifications, it's probably a reasonable drop-in replacement.
Is there a reason not to use something more common/standard like https://github.com/catchorg/Catch2? Catch2 is header-only and can be included directly into the repository so it adds no extra installation steps.
The text was updated successfully, but these errors were encountered:
I have no strong preference. I'm fine with using Catch2. But since I wrote the other unit testing framework (and it's also header-only), it came to mind first.
Currently, threads are only used for testing framework (and not testing cases themselves). IMO, it's better to shift responsibility for running tests in parallel to the testing environment (
make test -j8
) and decouple it from the testing code.Following a previous issue, #34:
Is there a reason not to use something more common/standard like https://github.com/catchorg/Catch2? Catch2 is header-only and can be included directly into the repository so it adds no extra installation steps.
The text was updated successfully, but these errors were encountered: