On 4/30/14, 7:18 AM, Ary Borenszweig wrote:
On 4/30/14, 6:43 AM, Dicebot wrote:
On Wednesday, 30 April 2014 at 07:14:34 UTC, Jacob Carlborg wrote:
But unit tests in D suck as well. I mean, how do I run a single unit
test in D?
This is common complaint I still fail to understand. I have never ever
wanted to run a single unit test, why would one need it? If running all
module tests at once creates problems than either module is too big or
unit tests are not really unit tests.
When I have a bug in my code I usually add a test for it so it never
happens again.
Because it's a bug, I might need to debug it. So I add a couple of
"writefln" instead of using a debugger (it's faster and I get formatted
results easier).
Now, if I run all tests I will get output from all the tests, not the
one I'm trying to debug. That's really annoying.
Yah, naming unittests is key here. With names one can specify which to
run/not run, regex patterns (i.e. "run only quick*") etc. -- Andrei
