True versus IsTrue, etc.
Charlie Poole
I'm cross-posting to the nunit and nunit-lite groups
since this concerns both.
Currently, I am working on consolidating code between
NUnit and NUnitLite. The latest code at
http://launchpad.net/nunitlite reflects this and I'll
do a release drop when I reach a plateau.
The objective is to remove any purely arbitrary
differences and to add new functionality that has
been developed in NUnit recently. Eventually, I
hope to build both frameworks from a common
codebase.
One difference between them is that NUnitLite
supports Assert.True, Assert.False, Assert.Null
and Assert.NotNull while the NUnit versions of
the same asserts use IsTrue, IsFalse, etc.
NUnit folks: these four are the *only* so-called
classic asserts in NUnitLite. Everything else
uses the constraint syntax.
Options I can see are:
1. Leave the difference - folks are used to it. This
means that code intended to compile against either
full NUnit or NUnitLite can't use these.
2. Change NUnitLite to use "Is" Personally I dislike
this but it's a valid possibility.
3. Change NUnit to *not* use Is for
3a) those particular asserts, OR
3b) all asserts
4. Support both versions in NUnit, possibly marking
the "Is" forms as obsolete.
5. Drop these items from NUnitLite and use various
forms of Assert.That instead.
What do you think?
Charlie