I have SpecFlow tests in a Visual Studio project and I'd like to get code coverage for those tests.
The thing is that I can't seem to get SpecFlow tests listed in Visual Studio Test Explorer for some reason, which is a prerequisite for running Visual Studio provided code coverage.
Just as a note, all other tests (regular and not SpecFlow) from other test projects are listed in the test explorer.
So, effectively, this question comes to:
How to get SpecFlow tests listed into Visual Studio Test Explorer window?
Related
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.
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 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 am running vs.net 2008 with nunit runner.
If I set a breakpoint in the unit test code, it just runs the unit test in the runner.
I'm guessing I have to integrate nunit with vs.net somehow?
My unit tests are just a class library project, I cannot run the tests in vs.net 2008, I can only do it via the runner currently.
If you want to debug in your current setup (running nunit runner that has your assemblies loaded), do the following:
Run nunit.exe
Open (or create) your nunit project (File > New/Open Project
Under Tools > Settings, click IDE Support > Visual Studio and check 'Enable Visual Studio Support'
Once your nunit file is setup and you are ready to run, go to VS and click Tools > Attach To Process...
Verify that 'Managed Code' is selected in the 'Attach to' area
Find unit.exe, select it, and click Attach
Place desired breakpoints in the library
From the nunit GUI, click Run
If youre debugging the correct assemblies, it should hit your breakpoint.
Ideally, I would change it to run nunit as an external program and supply your .nunit project file as the input. See here for more details.
I am running vs.net 2008 with nunit runner.
If I set a breakpoint in the unit test code, it just runs the unit test in the runner.
(emphasis mine)
You just answered your own question. Why would you expect the Visual Studio breakpoint to magically push you into Visual Studio when you don't run the code via Visual Studio in the first place?
I would recommend refactoring your tests so that as many tests as possible can be run through Visual Studio (see http://www.nunit.org/index.php?p=vsSupport&r=2.2.10 for details on NUnit support for Visual Studio), and then only run the remaining tests on the console.
To gain debugging unit tests with VS 2008, do the following:
1) Create project in NUnit runner and add your dll with unit tests into it.
2) Set up "Start external program" in your unit test project - NUnit exe file.
3)
When you debug set up your unit tests project as "startup
project" or whatever you have in VS2008.
4) Run
I'm new to NUnit and I just download it today and I can't get it working with visual studio. (I'm new to Visual Studio as well)
I'm following TekPub's Mastering C# 4.0 tutorial.
Screenshot: Something is missing within the red circle area. There should be some "green thing" on the side that let you double click on it and run the NUnit test.
http://dl.dropbox.com/u/20422001/NunitMissing.jpg
As you can see on the above screenshot, the NUnit seems not working....
Did I miss something? Please advice. Thanks
EDIT
This is how it SHOULD look like. I took a screenshot from the video tutorial:
http://dl.dropbox.com/u/20422001/nunit.jpg
and here is the project files:
http://dl.dropbox.com/u/20422001/MasteringCSharp.rar
As you can see, I don't have "Unit Test" Tab and "Unit Test Session"...
You aren't doing anything wrong. Out of the box, NUnit doesn't integrate directly with Visual Studio. The screenshot from the video appears to be using Resharper's test runner.
Typically testing with NUnit requires you to compile your test project and then load it into the NUnit GUI (nunit.exe) where the tests can be run from there. When using the NUnit GUI, the project will reload anytime the assembly is recompiled. (I sometimes prefer having this in a separate process as it doesn't tie up Visual Studio's UI, but that's a matter of preference.)
The added advantage of using a third party test runner like Resharper, TestDriven.net, Galileo, etc is that it allows you to run or debug the tests directly from within the IDE. You can accomplish the same thing using NUnit by configuring Visual Studio to attach to NUnit and debug your tests from the external process. This post shows you how.
I haven't seen that particular video, but it sounds like you need an NUnit test runner for Visual Studio.
Check out the following:
Visual NUnit 2010 - free!
TestDriven.net
ReSharper
That my friend is JetBrains' Resharper - it's a paid add-in to Visual Studio that allows you to run tests from within the IDE. Highly recommended if you're working for a prolonged period in VS.
Of course since you're just starting out, you could use the NUnit GUI to run your tests. You can also set it to run tests after each build.
Tools > Settings > Test Loader > Assembly Reload. Check "Re-Run last tests run". Apply changes