On 4/30/14, 9:19 AM, Byron wrote:
On Wed, 30 Apr 2014 09:02:54 -0700, Andrei Alexandrescu wrote:


I think indeed a small number of unittests rely on order of execution.
Those will be still runnable with a fork factor of 1. We'd need a way to
specify that - either a flag or:

static shared this() { Runtime.unittestThreads = 1; }


Andrei

Named tested seems like a no brainier to me.

Maybe nested unittests?

unittest OrderTests {
   // setup for all child tests?

   unittest a {

   }

   unittest b {

   }

}

I wouldn't want to get too excited about stuff without there being a need for it. We risk overcomplicating things (i.e what happens inside loops etc).

I also wonder if its just better to extend/expose the unittest API for
more advanced things like order of execution, test reporting, and parallel
execution. And we can just support an external unittesting library to do
all the advanced testing options.

That would be pretty rad.


Andrei

Reply via email to