mstest

I need to know how to tell MSTEST to run all test projects in a solution file. This needs to be done from the command line. Right now I have to pass it a specific project file, I'm trying to get it to run from a SOLUTION file. I'm hoping this is possible, because in Visual Studio, hitting Ctrl+R, A, runs ALL tests in the currently opened solution. The way I've interpretted the help files, you have to pass in each DLL specifically. I want to run this from the command line from my CruiseControl.NET server, so I can write other utilities to make this happen. If there is a wierd way of getting

I am using MSTest , and I want to set the same test category for all methods in test class at once, without setting TestCategory attribute to each method individually. How can this be done? The most convenient and obvious way would be to set TestCategory attribute on class, but it can be applied to methods only. The ultimate goal is to skip integration tests during test run on TFS check-in. To be able to set the [TestCategory] attribute at the class level, install the “MSTest V2” TestFramework using NuGet. Ref: https://blogs.msdn.microsoft.com/devops/2016/06/17/taking-the-mstest-framework

I have a test harness running and it was failing to run due to Type not resolved, which more specifically was a SerializationException on a bad bind. I used fuslogvw to track down where it was looking for the DLL and not finding it and I'm confused as to why it is looking in the location it is: === Pre-bind state information === LOG: DisplayName = DavisVision.Common.Data, Version=3.1.0.34, Culture=neutral, PublicKeyToken=c410b32babd148a6 (Fully-specified) LOG: Appbase = file:///C:/PROGRAM FILES (X86)/MICROSOFT VISUAL STUDIO 14.0/COMMON7/IDE/COMMONEXTENSIONS/MICROSOFT/TESTWINDOW/ LOG: Initial

Since the naming of a unit test method makes its purpose more meaningful, is it necessary to add a summary to a unit test method? Example: /// <summary> /// Check the FormatException should be thrown when a give country data line contains a invalid number. /// </summary> [TestMethod] public void FormatException_Should_Thrown_When_Parse_CountryLine_Containing_InvalidNumber() { ... } I think the long descriptive name is more important than the XML comment. Since the unit test isn't going to be part of an API, you don't need the XML comment. For Example: [TestMethod] public void FormatException

how can I set the working directory for MS Tests projects, like I can do it for normal application projects? My Component that is tested need to access some config files that are also used by other applications. So far I have to copy these files the bin/debug folder of my test project, as these files are expected to be in the working directory. Is it possible to set a working directory for test projects? For those who use Visual Studio 2012, if you set the output directory of the test project under Properties|Build|OutputPath then that will become the working directory when you run the tests