Le 30/04/2014 18:19, Byron a écrit :
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 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.
I don't see the usage? I'll find nice enough if IDEs will be able to put
unittest in a tree and using the module's names for the hierarchy.
