So Visual Studio doesn't seem to register all my Unit Tests. I have no idea how to solve this, and google hasn't been able to help.
Most of the tests is for some reason labeled as "Inconclusive Tests". This is how the built in Unit Tests displays:
P.S. The test runner works fine when I run the tests in a terminal.
.NET Core test projects in Visual Studio for Mac 7.2 has a bug that would cause the test names to appear blank in the Unit Tests window. This problem was fixed in Visual Studio for Mac 7.3.
Related
I'm assisting another developer who's using NUnit with Visual Studio 2017. She's running unit tests and it appears that they're all getting run but for some reason on some of the tests, the ambient test indicators simply don't show up.
I am not totally sure of the version of NUnit but I think it's 2.6.x. The tests are showing up in the test explorer (I've seen that issue before with VS 2017) and, as I say, it looks like they're actually running.
It looks like the ambient indicator doesn't show up for tests decorated with the [TestCase] attribute. Is this a known issue? She just wants to make sure this isn't indicating some other problem.
EDIT: I can reproduce this behavior with NUnit (3.8.1) and NUnit3TestAdapter (3.8.0) both installed via NuGet. VS Professional 2017 v 15.3.5
Neither the integrated test environment nor Resharper won't run any unit tests.
When starting Visual Studio the Test Output Pane shows 10+ lines stating:
An exception was thrown while initializing part "Microsoft.VisualStudio.TestWindow.Controller.TestPlatformProvider".
This is what I've tried so far:
Clear folder %LocalAppData%\Microsoft\VisualStudio\14.0\ComponentModelCache
Create a simple test project with one class library, one class and one test library containing one unit test for that class
Uninstallation and new installation of Visual Studio 2015
All actions didn't fix the problem. Even the simple test won't run.
Running tests from command line using MSTest does work.
Ensure that your anti-virus programs are not quarantining Visual Studio components.
I had this problem when our corporate IT department changed our Sophos Protection Quarantine policy. VS2015 Unit testing stopped working for everyone, with a similar error.
I have been trying to run my own test method in orchard cms , but visual studio does not detect test projects in the solution.is there any specific method to run tests in orchard?or this is a problem with visual studio itself not detecting the test classes.
thanks for your help.
Orchard uses NUnit tests, so you should install NUnit in your Visual Studio to be able to run the tests.
I hope some one has an idea why Ctrl+R, T is not working in VS2013 anymore.
Previously (VS2012) when I hit the shortcut, and I had my cursor in a test, it only runs the test.
At the website of Microsoft it says exactly how I should expect it should work.
It says:
Ctrl + R, then press T
This runs the tests in the current scope. That is, it runs the
current test method, all the tests in the current test class, or
all the tests in the namespace, respectively.
Source: http://msdn.microsoft.com/en-us/library/vstudio/ms182470.aspx#RunTestsFromTestProject
However in VS2013 it runs all the tests in the current file.
When I use the Test Explorer it runs correctly the only selected test...
I have the following extensions installed:
Productivity Power Tools 2013
Xunit.net runner for Visual Studio 2012 and 2013
Chutzpah Test Adapter for the Test Explorer
Chutzpah Test Runner Context Menu Extension
Ok, its a bug in the xUnit testrunner.
I tested with NUnit and it works as expected.
On xUnit.net is a bugreport.
Link: http://xunit.codeplex.com/workitem/9901
Edit:
Issue is solved in version 0.99.2
I need to come of with the approach where:
I need to run Visual Studio Unit/Integration tests in environment where visual studio will not be installed.
After lots of fiddling around i came up with one approach that is to copy MSTest.exe and related dlls into the machine and run the tests from command line.
As shown here (http://msdn.microsoft.com/en-us/library/ms182486.aspx)
But wondering is this the only solution to run visual studio tests, i.e Normal MSTests in the environment where there is no visual studio?
Any help from experienced geeks will really help :) :)