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
You have a local file named unittest.py that is being imported instead: /home/mariusz/Pulpit/unittest.py Rename that file or remove it altogether. Make sure you remove any corresponding unittest.pyc file in the same folder if it is there. The file is masking the standard library package.
Try ClassLoader loader = getClass().getClassLoader(); setDefaultAssertionStatus(true); or ClassLoader.getSystemClassLoader().setDefaultAssertionStatus(true); EDIT: based on the comments ClassLoader loader = ClassLoader.getSystemClassLoader(); loader.setDefaultAssertionStatus(true); Class<?> c = loader.loadClass(“MyClass”); MyClass myObj = (MyClass) c.newInstance(); public class MyClass { private static final int foo[] = new int[]{4,5,67}; MyClass() { assert foo.length == 10; } }
Instead of assertions in the setup to check the result, I used a simple test (a test method along the others, but positionned as first test method). I have seen several advantages: The setup keeps short and focused, for readability. The assertions are run only once, which is more efficient. Usage and discussion : For … Read more
First, the performance difference can be huge. In one project our asserts literally caused a 3x slowdown. But they helped us uncover some really pesky bugs. Which is exactly the point. Asserts are there to help you catch bugs. And because they are removed in release builds, we can afford to put a lot of … Read more
Contrary to the conventional wisdom, asserts do have a runtime impact and may affect performance. The impact is likely to be small on average and zero in the median case, but it could be large when the stars align just right. Some of the mechanisms by which asserts slow things down at runtime are fairly … Read more
Google test provides ASSERT_DEATH, EXPECT_DEATH and other related macros. This question and What are Google Test, Death Tests are each other’s answers. Does that make them duplicates, or not? 😉
Don’t use if(Dispatcher.CurrentDispatcher.Thread == Thread.CurrentThread) { // Do something } Dispatcher.CurrentDispatcher will, if the current thread do not have a dispatcher, create and return a new Dispatcher associated with the current thread. Instead do like this Dispatcher dispatcher = Dispatcher.FromThread(Thread.CurrentThread); if (dispatcher != null) { // We know the thread have a dispatcher that we … Read more
A compile-time assert in pure standard C is possible, and a little bit of preprocessor trickery makes its usage look just as clean as the runtime usage of assert(). The key trick is to find a construct that can be evaluated at compile time and can cause an error for some values. One answer is … Read more
assertTrue will fail if the second parameter evaluates to false (in other words, it ensures that the value is true). assertFalse does the opposite. assertTrue(“This will succeed.”, true); assertTrue(“This will fail!”, false); assertFalse(“This will succeed.”, false); assertFalse(“This will fail!”, true); As with many other things, the best way to become familiar with these methods is … Read more