mstest

Is there a way I can add a custom message to the result of a test method? I want to put a stopwatch on part of the code to see how long its running. I don't need to test that it's running within a certain time frame, just want to see in the result window what the elapsed time was. Assuming you are using MSTest, you can use System.Diagnostics.Trace.WriteLine("Hello World"); To output whatever you'd like. It will show up in the full results of the test runner. The example above did not work for me but the following did: var result = routeManager.UpdateWalkingOrder(previouspremiseFuncLoc,

I have upgraded from Visual Studio 2010 to Visual Studio 2012. In my unit test project, I have a [ClassInitialize] method which generates a CSV file which I then feed into a data-driven [TestMethod] using [DataSource] connected to the CSV. This works great in Visual Studio 2010. I cannot get this to work in Visual Studio 2012. It seems that in VS2012 the MS test runner requires the file connected to the [DataSource] to already exist otherwise none of the tests will run. If I create the CSV myself, the data-driven tests run, but they do not pick up the data created in [ClassInitialize]: it

Using MSTest, I needed to obtain the name of the current test from within the [TestInitialize] method. You can get this from the TestContext.TestName property. I found an unexpected difference in behaviour between a static TestContext that is passed in to the [ClassInitialize] method and one that is declared as a public property (and gets set by the test runner). Consider the following code: using System; using Microsoft.VisualStudio.TestTools.UnitTesting; namespace TestContext.Tests { [TestClass] public class UnitTest1 { public TestContext TestContext { get; set; } private static TestContext

I have not been able to debug or step through unit test. Here is my sample test code... using System; using System.Text; using System.Collections.Generic; using System.Linq; using Microsoft.VisualStudio.TestTools.UnitTesting; using DomainModel.Entities; using DomainModel.Abstract; using WebUI.Controllers; namespace Tests { [TestClass] public class PeopleControllerTests { static IPeopleRepository MockPeopleRepository(params Person[] people) { var mockPeopleRepos = new Moq.Mock<IPeopleRepository>(); mockPeopleRepos.Setup(x => x.People).Returns(people.AsQueryable()); return mockPeopleRepos.Object

From reasons I won't get into, all our unit tests are using the VSTS test framework. I now want to create an MSBuild script that runs the tests, but I don't want to use mstest.exe from various reasons (it's slower, requires Visual Studio installation everywhere, I need to maintain testrunconfig, etc.) I've seen that TestDriven.net and TeamCity are able to run VSTS tests 'NUnit style', without using mstest.exe. Are you aware of any standalone command line utility that does this? You can execute Team System Tests (MSTest) in NUnit if you use a special NUnit Addin that recognizes the MS Test

I am seeing this error when I try to run unit tests: Testhost process exited with error: It was not possible to find any compatible framework version The specified framework 'Microsoft.NETCore.App', version '1.1.2' was not found. - Check application dependencies and target a framework version installed at: \ - Alternatively, install the framework version '1.1.2'. How to fix it? Installing DotNetCore.1.0.5_1.1.2-WindowsHosting solved the problem for me and my collegues. abdallah mahmoud The error tells you that you need to download Microsoft.NETCore.App , version 1.1.2 you can install it

I realise that there are many older questions addressing the general question of NUnit v MSTest for versions of Visual Studio up to 2008 (such as this one ). Microsoft have a history of getting things right in their 3rd version. For MSTest, that is VS2010. Have they done so with MSTest ? Would you use it in a new project in preference to NUnit? My specific concerns: speed running tests within CruiseControl.NET (either commandline or MSBuild task) code coverage reports from CC.NET can you run MSTest tests in debug mode (We use ReSharper, so test-runners are not an issue for us. We have used