Re: Unit-threaded v0.4.0 released

2014-05-03 Thread Atila Neves via Digitalmars-d-announce

Version v0.4.3 now. New:

. Tests can be run in random (single-threaded) order. A seed can 
be specified.
. unittest blocks are registered at compile-time. This mean each 
block/function
is its own test case. Before all blocks from a module were a test 
case.


Atila

On Wednesday, 23 April 2014 at 07:42:57 UTC, Atila Neves wrote:

http://code.dlang.org/packages/unit-threaded

. The @HiddenTest UDA now takes a compile-time string meant to 
be a bug id or other reason why the test is hidden. 
Unfortunately that means previous code using it needs to add a 
string or it'll fail to compile
. The new @ShouldFail UDA also takes a compile-time string for 
the same reason. This fauses a test to fail unless it throws. 
Harder to sweep under the carpet than @HiddenTest
. On the sweeping front, the number of hidden tests is now 
reported in yellow
. Exceptions that aren't a descendant of 
unit_threaded.check.UnitTestException display a stack trace. 
This is for easier debugging in case an unexpected exception is 
thrown

. The one bug I knew of was fixed

Atila




Unit-threaded v0.4.0 released

2014-04-23 Thread Atila Neves via Digitalmars-d-announce

http://code.dlang.org/packages/unit-threaded

. The @HiddenTest UDA now takes a compile-time string meant to be 
a bug id or other reason why the test is hidden. Unfortunately 
that means previous code using it needs to add a string or it'll 
fail to compile
. The new @ShouldFail UDA also takes a compile-time string for 
the same reason. This fauses a test to fail unless it throws. 
Harder to sweep under the carpet than @HiddenTest
. On the sweeping front, the number of hidden tests is now 
reported in yellow
. Exceptions that aren't a descendant of 
unit_threaded.check.UnitTestException display a stack trace. This 
is for easier debugging in case an unexpected exception is thrown

. The one bug I knew of was fixed

Atila