The JUnit framework captures only assertion errors in the main thread running the test. It is not aware of exceptions from within new spawn threads. In order to do it right, you should communicate the thread’s termination state to the main thread. You should synchronize the threads correctly, and use some kind of shared variable … Read more
Undefine the NDEBUG macro – you can do this locally around the asserts you want to remain in the build: #undef NDEBUG #include <assert.h> // reinclude the header to update the definition of assert() or do whatever you need to do so your build process does not define the NDEBUG macro in the first place.
Assertions should be used for expressing invariants, or preconditions. In your example, you are using them for checking unexpected input – and that’s a completely different class of exceptions. Depending on the requirements, it may be perfectly OK to raise an exception on wrong input, and stop the application; however the code should always be … Read more
If compiling in release mode includes defining NDEBUG, then yes. See assert (CRT)
The corresponding kernel macros are BUG_ON and WARN_ON. The former is for when you want to make the kernel panic and bring the system down (i.e., unrecoverable error). The latter is for when you want to log something to the kernel log (viewable via dmesg). As @Michael says, in the kernel, you need to validate … Read more
An assertion is similar to an if, it verifies the expression you provide: if the expression is true it continues the execution to the next statement (and prints nothing), if the expression is false, it raises an AssertionError. You can customize the error message providing a message separated by a colon like this: assert 4 … Read more
inspect.ismethod is what you want to find out if you definitely have a method, rather than just something you can call. import inspect def foo(): pass class Test(object): def method(self): pass print inspect.ismethod(foo) # False print inspect.ismethod(Test) # False print inspect.ismethod(Test.method) # True print inspect.ismethod(Test().method) # True print callable(foo) # True print callable(Test) # True … Read more
The main reason assertions are not used is because they are not enabled by default. Therefore if you have a condition that is important enough to require an assertion you can’t rely on assertions being enabled to get the job done. As other answers have correctly stated they’re designed for development-time testing and debugging because … Read more
Assertions are not for parameter checking. Parameter checking should always be done (and precisely according to what pre-conditions are specified in your documentation and/or specification), and the ArgumentOutOfRangeException thrown as necessary. Assertions are for testing for “impossible” situations, i.e., things that you (in your program logic) assume are true. The assertions are there to tell … Read more
The path described by LOCAL_INSTALL_DIR either does not exist, is a broken symbolic link, or you do not have permission to stat() it.