Comments on: DUnitAssertions: Epsilons

By: Ajasja

Ajasja — Thu, 19 Apr 2007 05:48:00 +0000

I’d go for the first or the last one.

But that’s just a feeling (and not based on, for example, years of experience:)

By: Joe White

Joe White — Wed, 18 Apr 2007 01:29:00 +0000

Tis.EqualTo (and its siblings Tis.GreaterThan, Tis.Not.EqualTo, etc.) returns a constraint, which is a hybrid type (essentially an interface reference).

Expect.That then calls methods on the constraint to decide whether the constraint matches the actual value, and if not, to generate the failure message ("Expected… but was…") and throw an exception.

Currently I’m also leaning toward the first example, because it’s easiest from an implementation standpoint right now. But if I can think of something that’s more readable, I’ll work it in — after all, you read test code a lot more often than you write it.

By: Brad White

Brad White — Tue, 17 Apr 2007 19:29:00 +0000

That depends, of course.
What are the other methods of Tis?

What does EqualTo return?

At first glance I would expect that EqualTo should take the epsilon. Your first example.
But that depends on what EqualTo does.