Board index » delphi » Re: Assert for DUnit v1.2

2008-01-09 07:56:23 AM
delphi113
Tjipke,
You may not be aware of DUnit 2. See
members.optusnet.com.au/~mcnabp/ for further details.
Regards, Peter Evans
 

Interesting, but there are already some similar projects:
dSpec: sourceforge.net/projects/dspec
Specify.That(Foo).Should.Equal(3);
Specify.That(Bar).Should.Be.OfType(TBlueWidget);
Specify.That(Baz).Should.Be.GreaterThan(50).And.Be.LessThan(60);
DUnitAssertions: excastle.com/blog/archive/2007/04/04/36188.aspx
Expect.That(2 + 2, Tis.EqualTo(4));
Expect.That(2 + 2, Tis.Not.EqualTo(5));
DUnitLite: code.google.com/p/dunitlite/
Specify.That(Foo, Should.Be.AtLeast(45));
Specify.That(Foo, Should.Be.AtMost(45));
Specify.That(Foo, Should.Be.Between(45, 48));
Specify.That(Foo, Should.Be.GreaterThan(45));
Specify.That(Foo, Should.Be.InRange(45, 48));
Specify.That(Foo, Should.Be.LessThan(45));
btw, thanks for the link of DUnit 2, Peter.
Regards,
Beta.
 

possibilities (like StringAssert, CollectionAssert or whatever you can think
of :-))
development of it. I did scan the document of DUnit2 and one thing I noticed
that DUnit2 is not creating an instance of the testclass for each test and
DUnit is? The creating an instance for each test has the advantage that
multithreaded execution of tests is easier: each test can have its own
instance. See also:
blogs.msdn.com/nnaderi/archive/2007/02/17/explaining-execution-order.aspx
where Naysawn Naderi mentions that MSTest is using an instance for each test
and NUnit is not. MSTest does parallel executing of tests: and I think that
is the way to go in this age of multicore processors. (I also thought about
extending DUnit for parallel testing, but since there are only 24 hours in a
day...)
Thanks for you time,
Tjipke
--
Need to change your projects version info from the commandline?
Use ChangeRes: www.tiriss.com/changeres
 

DUnitAssertions is renamed to DUnitLite (see
excastle.com/blog/archive/2007/05/19/41879.aspx)
(To bad Joe was a litle earlier with DUnitAssertions, otherwise I'd have
used that name :-)
The goals of dSpec and DUnitLite are more oriented to writing more readable
tests, where Assert for DUnits goal is to be able to write tests in the same
style as NUnit and MSTest. (And so only having to learn one syntax...)
Regards,
Tjipke van der Plaats
--
Need to change your projects version info from the commandline?
Use ChangeRes: www.tiriss.com/changeres
 

Tjipke A. van der Plaats wrote :
From what I understand in one case the testclass is created once for
every method declared in it while in dUnit2 it is created once when it
is registered in the test factory. I might be wrong though I haven't
read it carefully enough either.
regards
Yannis.
--
You talk a great deal about building a better world for your children,
but when you are young you can no more envision a world inherited by
your children than you can conceive of dying. The society you mold, you
mold for yourself.
----Russell Baker-------