On Monday, 23 September 2013 at 16:40:56 UTC, jostly wrote:
Let's not end up in that situation, but rather work out a
common API to run unit tests, and the D unit test community can
be the envy of every other unit tester. :)
You've raised some nice ideas and got me thinking. However, i do
think we are missing some way of knowing when unit tests start
and stop. I like the built in unittest blocks but it would be
nice to have something like:
beforetests
{
...
}
aftertests
{
...
}
To apply code before and after the unit tests have run. These
could be used to setup and the execute the reporting environment?
I can't think of a way to do this automatically without these
constructs.
