Disable Running Tests automatically about ut HOT 3 CLOSED

I’d really appreciate that.

from ut.

🤔 With the assumption that the library is well tested the integration might be done with BUILD_TESTS=OFF. I personally believe that building and running tests is the thing (for example static_asserts tests). But I agree it's annoying to integrate if tests aren't passing in any env and that should be addressed IMHO by finding and fixing the root cause 🤔

from ut.

1. One of the simplest examples of why it might be preferred to have all the tests run as their own step is that more information can be gleaned from the results of multiple tests. If tests stop running after the first failed test, you get less information.

2. Consumers of your library may be on a time-crunch where they just need to build their project, ensure that a single failing test in your library is non-serious, and move on to their primary task at the moment. Of course, you have to hope they will take the time later to submit an issue. 😅

3. Last, CMake splits building and testing into separate steps as seen in ExternalProject_Add. CMake typically prefers running tests after building a project through the use of its CTest/CDash functionality which can additionally handle submitting test results to CI dashboards.

from ut.