vs-unit-testing-framework

When running code coverage for my solution which contains multiple projects, I noticed that Code Coverage includes also my test assemblies. I found an article which suggests the following template for .runsettings: <?xml version="1.0" encoding="utf-8"?> <RunSettings> <DataCollectionRunSettings> <DataCollectors> <DataCollector friendlyName="Code Coverage" uri="datacollector://Microsoft/CodeCoverage/2.0" assemblyQualifiedName="Microsoft.VisualStudio.Coverage.DynamicCoverageDataCollector, Microsoft.VisualStudio.TraceCollector, Version=11.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a">

I am writing a unit test for a controller like this: public HttpResponseMessage PostLogin(LoginModel model) { if (!ModelState.IsValid) return new HttpResponseMessage(HttpStatusCode.BadRequest); } the model looks like: public class LoginModel { [Required] public string Username { set; get; } [Required] public string Password { set; get; } } Then I have unit test like this one: [TestMethod] public void TestLogin_InvalidModel() { AccountController controller = CreateAccountController(); ... var response = controller.PostLogin(new LoginModel() { }); Assert.AreEqual(HttpStatusCode.BadRequest,

I'm using Visual Studio 2010 Beta 2. I've got a single [TestClass] , which has a [TestInitialize] , [TestCleanup] and a few [TestMethods] . Every time a test method is run, the initialize and cleanup methods are ALSO run! I was under the impression that the [TestInitialize] & [TestCleanup] should only be run once, per local test run. Is that correct? If not, what is the proper way to do this? alexn TestInitialize and TestCleanup are ran before and after each test, this is to ensure that no tests are coupled. If you want to run methods before and after ALL tests, decorate relevant methods with

What is the difference between TestInitialize vs ClassInitialize in MSTest? What are the pros cons of each? I'm under the impression that TestInitialze should run with EACH test, every time? Is that correct? And that ClassInitialize will run every time a new instance of any class? Both attributes are available only for the classes (and hence tests) where they belong. TestInitialize runs before every test that is declared on the the same class where the attribute is declared. ClassInitialize runs only on the initialization of the class where the attribute is declared. In other words it won't