MSTest can be used without installing Visual Studio. You will need to install Visual Studio Test Agent, which is a free download from Microsoft. I think this approach is better from a licensing perspective than manually copying MSTest.exe and its dependencies onto the build server. See this blog for reference: http://blogs.msdn.com/b/anutthara/archive/2009/12/16/running-tests-in-mstest-without-installing-the-vs-ide.aspx
I experienced this error after removing all nuget packages as I had changed my .net version and did not need any of them to compile. After re-installing the MSTest.TestAdapter nuget package ReSharper started running my unit tests again as expected. Install-Package MSTest.TestAdapter
Recently when I have encountered problems such as this, I add a new Build Configuration to the visual studio project named something such as “Local Developer Debug” and use the settings from the existing Debug configuration. Then I go to “Project -> MyProjectName Properties -> Build”, make sure “Local Developer Debug” is the selected configuration … Read more
Best thing one can do until something is implemented in the library is to use Xunit.SkippableFact: [SkippableFact] public void SomeTest() { var canRunTest = CheckSomething(); Skip.IfNot(canRunTest); // Normal test code } This will at least make it show up as a yellow ignored test case in the list. Credit goes to https://stackoverflow.com/a/35871507/537842
There is a good walkthrough originally published at https://blogs.msmvps.com/bsonnino/2017/03/18/parametrized-tests-with-ms-test (link is now to archive by wayback machine). In a nutshell, you will need to install MSTest.TestFramework and MSTest.TestAdapter, and remove references to Microsoft.VisualStudio.QualityTools.UnitTestFramework. You can then indicate a parameterised test with the [DataTestMethod] attribute, and can add your parameters using the [DataRow] attribute, as per … Read more
When using Microsoft.VisualStudio.TestTools.UnitTesting, go to ‘Test’ in the main menu of VS 2010, click submenu ‘Debug’ -> ‘tests in current context’. Right-clicking on the test-code and selecting ‘run tests’ will never start the debugger, not even when mode = debug.
Try: AppDomain.CurrentDomain.SetData( “DataDirectory”, Path.Combine(AppDomain.CurrentDomain.BaseDirectory, “”)); This will Create Db File on /bin/Debug/yourdbname.mdf
It took me a few tries to find the answer in Google, so I’m putting it here in case anyone else runs into the same problem. A detailed description can be found at this blog posting. Basically, the fix invovles right-clicking on the dll file (xunit.dll for example) in Windows Explorer, going to Properties, and … Read more
I had to add the following Nuget packages: MSTest.TestAdapter MSTest.TestFramework Microsoft.NET.Test.Sdk Visual Studio release notes
It appears that the VSMDI problem is a known bug and has been around since VS2005 Team System but it has no clear fix as yet. Another reason to NOT use MS Test. An MSDN blog details how to run unit tests without VSMDI files.