In MbUnit you can do something like this:
[Test] [TestCategory("Bad Arguments")] [TestCategory("Fast")] [ExpectedException(typeof(ArgumentNullException))] public void TestCopyWithBadHref() { . . . }
Pay attention to the following two:
[TestCategory("Bad Arguments")] [TestCategory("Fast")]
Since TeamBuild can be integrated with MsTest to perform closed check-ins and / or run at night, this is a great opportunity! However, given that some tests can be performed for a long time, it is convenient to divide them into those tests that must be performed before confirming each registration, as well as those tests that should be performed at night instead of their duration, as well as other factors.
One way to achieve this can be to create several projects - one for slow tests, one for quick tests, etc. However, this separation is inconvenient. Project dependencies will not be considered natural, and some tests may be in more than one logical category.
It would be great if MsTest had something similar to what MbUnit had for a long time. For example, you can run MbUnit.Cons.exe and specify the category that will be used using the command line.
How can I achieve the same using MsTest ? We are an MSFT store and I was not able to sell MbUnit to my employees.
unit-testing mstest mbunit
Hamish grubijan
source share