Your macro can contain the __FUNCTION__ macro. Make no mistake, the function name will be inserted into the expanded code at compile time, but it will be the correct function name for each call to your macro. So it “seems like” it happens in run-time 😉 e.g. #define THROW_IF(val) if (val) throw “error in ” … Read more
Rock solid for 4 days straight. I’m declaring victory on this one. The answer is “stupid user error” (see comments above). A mutex should only be unlocked by the thread that locked it. Thanks for bearing with me.
If you’re calling sendmail with a named parameter subject then it’s better to check whether the named argument matches what you expect: args, kwargs = self.myclass.sendmail.call_args self.assertEqual(kwargs[‘subject’], “Hello World”) This does assume both implementations of sendmail have a named parameter called subject. If that’s not the case you can do the same with a positional … Read more
If you look at the code in Predef.scala you’ll see that all three do very similar job: def assert(assertion: Boolean) { if (!assertion) throw new java.lang.AssertionError(“assertion failed”) } def assume(assumption: Boolean) { if (!assumption) throw new java.lang.AssertionError(“assumption failed”) } def require(requirement: Boolean) { if (!requirement) throw new IllegalArgumentException(“requirement failed”) } There are also versions which … Read more
Rather than provide a bunch of different assertions as you suggest, Test::Unit provides the method assert_operator, used like this: assert_operator x, :>, y assert_operator x, :>=, y etc.
No difference. Assert.True() and others (without Is) were added since v2.5. From documentation for the version 2.5: (nunit v2.5) Two forms are provided for the True, False, Null and NotNull conditions. The “Is” forms are compatible with earlier versions of the NUnit framework, while those without “Is” are provided for compatibility with NUnitLite BTW, Disassembled … Read more
This is a perfectly valid question. First of all, many people are suggesting that you are using assertions wrongly. I think many debugging experts would disagree. Although it is good practice to check invariants with assertions, assertions shouldn’t be limited to state invariants. In fact, many expert debuggers will tell you to assert any conditions … Read more
Another use for the -O flag is that the value of the __debug__ builtin variable is set to False. So, basically, your code can have a lot of “debugging” paths like: if __debug__: # output all your favourite debugging information # and then more which, when running under -O, won’t even be included as bytecode … Read more
In short, don’t use it; use <assert.h>. C++11 removed any formal guarantee of a “c….” header not polluting the global namespace. It was never an in-practice guarantee, and now it’s not even a formal guarantee. Hence, with C++11 there is no longer any conceivable advantage in using the “c….” header variants, while there is the … Read more
Sometimes I have exactly one assert per test case, but I think more often I have several assert statements. I’ve seen the case that @Arkain eludes to, where a very large piece of code has a single unit test suite with just a few test cases, and they are all labeled testCase1, testCase2, etc, and … Read more