VSTS unit test asserts and MbUnit
My last post looked at MbUnit and NUnit so out of interest I thought I would take a look at the VSTS unit test asserts and how they stacked against MbUnit.
VSTS Assert
AreEqual - MbUnit
AreNotEqual - Not supported
AreNotSame - MbUnit
AreSame - MbUnit
Equals - Not supported
Fail - MbUnit
Inconclusive - MbUnit Warning is closest
IsFalse - MbUnit
IsInstanceOfType - Not supported
IsNotInstanceOfType - Not supported
IsNotNull - MbUnit
IsNull MbUnit
IsTrue - MbUnit
ReferanceEquals - MbUnit
VSTS StringAssert
Contains - Not supported
DoesNotMatch - MbUnit DoesNotContain is closest
EndsWith - MbUnit
Matches - MbUnit fullmatchh is closest
StartsWith - MbUnit
VSTS CollectionAssert
AllItemsAreInstancesOfType - Not supported, MbUnit Equals could be used
AllItemsAreNotNull - Not supported, MbUnit Equals could be used
AllItemsAreUnique - Not supported, MbUnit Equals could be used
AreEqual - MbUnit
AreEquivalent - Not supported, MbUnit IsSyncronised could be used
AreNotEqual - Not supported, MbUnit IsSyncronised could be used
AreNotEquivalent - Not supported, MbUnit IsNotSyncronised could be used
Contains - Not supported, MbUnit Equals could be used
DoesNotContain - Not supported, MbUnit IsNotSyncronised could be used
IsNotSubsetOf - Not supported
IsSubsetOf - Not Supported
As per my last post MbUnit has a greater degree of Asserts in it's toolbox ready for you to use.