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 has a lot of asserts that you can use in your testing toolbox. To help you see the difference between unit test frameworks I have compared the asserts from the current NUnit release to the current MbUnit release as follows. AreEqual - NUnit AreNotSame - NUnit AreSame - NUnit AreValueEqual Between...

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 has a lot of asserts that you can use in your testing toolbox. To help you see the difference between unit test frameworks I have compared the asserts from the current NUnit release to the current MbUnit release as follows. AreEqual - NUnit AreNotSame - NUnit AreSame - NUnit AreValueEqual Between...

Lost in translation some place was the credit that Roy fully deserves for being the man to come up with the concept for the database testing attributes and fixtures in MbUnit . Roy emailed me last week to voice some concerns for credit and in return I have edited the MbUnit wiki . If your not sure what...

Another handy VSTS feature is that you can test ASP.NET code behind with FxCop, I can't seem to find a way to simply do this using the FxCop GUI or command line for CCNet. Any approaches or suggestions welcome. Update: A bit ad-hoc but I came up with the following Go to C:\WINDOWS\Microsoft.NET\Framework...

I really like the fact you can run FxCop direct from VS in VSTS, I really want that from my plain old VS. While researching I found two ways. VS external tools You can set up FxCop to run inside of the VS command window, the reporting is not great but you could change the options to report to a file...

Lost in translation some place was the credit that Roy fully deserves for being the man to come up with the concept for the database testing attributes and fixtures in MbUnit . Roy emailed me last week to voice some concerns for credit and in return I have edited the MbUnit wiki . If your not sure what...

Another handy VSTS feature is that you can test ASP.NET code behind with FxCop, I can't seem to find a way to simply do this using the FxCop GUI or command line for CCNet. Any approaches or suggestions welcome. Update: A bit ad-hoc but I came up with the following Go to C:\WINDOWS\Microsoft.NET\Framework...

I really like the fact you can run FxCop direct from VS in VSTS, I really want that from my plain old VS. While researching I found two ways. VS external tools You can set up FxCop to run inside of the VS command window, the reporting is not great but you could change the options to report to a file...