Redundant assert statements in .NET unit test framework

Posted by Prabhu on Stack Overflow See other posts from Stack Overflow or by Prabhu
Published on 2010-06-15T21:33:55Z Indexed on 2010/06/15 21:52 UTC
Read the original article Hit count: 221

Filed under:
|
|
|
|

Isn't it true that every assert statement can be translated to an Assert.IsTrue, since by definition, you are asserting whether something is true or false?

Why is it that test frameworks introduce options like AreEquals, IsNotNull, and especially IsFalse? I feel I spend too much time thinking about which Assert to use when I write unit tests.

© Stack Overflow or respective owner

Related posts about c#

Related posts about .NET