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, the tests cannot be run by invoking the test-executable.
This is because the very first test ( "Parse help", "[help]" ) leads to exit(0) being called inside a callback created in void enable_help(). After that, the test executable exits. The checks contained in that test are never executed. Also, no further tests are executed. This means that whenever ( "Parse help", "[help]" ) is included in the list of tests to be run, some or all of the tests will not be run at all, depending on the order of tests.
It seems that this callback really should quit the program when used in user code. Hence, I don't know how to best solve this problem for the unit tests. Perhaps the problematic test case should be removed, especially since it doesn't actually test anything?
As an aside, perhaps the pragma warning modification (which are specific to MSVS compiler) to really be specific to that compiler, e.g., like this:
#if defined(_MSC_VER)
// pragma ...
#endif
Other compilers don't support this and the pragma sometimes becomes a warning in itself, as in "unknown pragma".
The text was updated successfully, but these errors were encountered:
Currently, the tests cannot be run by invoking the test-executable.
This is because the very first test
( "Parse help", "[help]" )
leads toexit(0)
being called inside a callback created invoid enable_help()
. After that, the test executable exits. The checks contained in that test are never executed. Also, no further tests are executed. This means that whenever( "Parse help", "[help]" )
is included in the list of tests to be run, some or all of the tests will not be run at all, depending on the order of tests.The callback looks like this:
It seems that this callback really should quit the program when used in user code. Hence, I don't know how to best solve this problem for the unit tests. Perhaps the problematic test case should be removed, especially since it doesn't actually test anything?
As an aside, perhaps the
pragma
warning modification (which are specific to MSVS compiler) to really be specific to that compiler, e.g., like this:Other compilers don't support this and the pragma sometimes becomes a warning in itself, as in "unknown pragma".
The text was updated successfully, but these errors were encountered: