Built tests are not added to the Visual Studio Test Explorer window

Question

I set up the SpecFlow plug-in for the Visual Studio 2013.
I created new Feature Item and build it.

Result: built test is not shown in the Test Explorer. Why?

I do it according to this video

have you added the specflow visual studio extension AND the nuget package? — Sam Holder, Jun 01 '15 at 13:11
Yes of course, I added the SpecFlow AND the SpecFlow.NUnit packeges — Vlad Kostyukevich, Jun 01 '15 at 16:05
added an answer showing how to set the configuration correctly — Sam Holder, Jun 01 '15 at 19:29

score 23 · Accepted Answer · answered Jun 01 '15 at 17:52

23

in order to configure it to generate MSTest tests you need to add this to your app.config:

<specFlow>    
  <unitTestProvider name="MSTest"></unitTestProvider>
</specFlow>

answered Jun 01 '15 at 17:52

Sam Holder

32,535
13
101
181

1

I have these rows in my app.config: – Vlad Kostyukevich Jun 02 '15 at 08:23
then your tests are generated in NUnit format and I don't think VS will recognise them by default. Either change it to MSTest (if you want to use MSTest) or install the specflow NUnit support NuGet package – Sam Holder Jun 02 '15 at 08:25
1

But SpecFlow.NUnit package is already installed but VS is still not see this test – Vlad Kostyukevich Jun 02 '15 at 08:31
does it see it if you change it to MSTest? – Sam Holder Jun 02 '15 at 08:45
[this might also be relevant](http://stackoverflow.com/questions/19298347/nunit-unit-tests-not-showing-in-test-explorer-with-test-adapter-is-installed) – Sam Holder Jun 02 '15 at 08:46
1

The type or namespace name 'TestTools' does not exist in the namespace 'Microsoft.VisualStudio' (are you missing an assembly reference?) - Error with – Vlad Kostyukevich Jun 02 '15 at 10:50
you have to add a reference to Microsoft.VisualStudio.QualityTestTools.UnitTestFramework.dll before they will run – Sam Holder Jun 02 '15 at 10:57
Solved my problem. Someone had overwritten our app.config file. – Sean Duggan Nov 19 '15 at 18:02

score 23 · Answer 2 · answered Jan 01 '16 at 12:58

I experience this same problem, but the solution was different.

Following the advice on a SpecFlow Github issue, the following worked for me:

Close all Visual Studio instances
Go to %TEMP%\VisualStudioTestExplorerExtensions\
Delete all the folders in here
Try again

score 17 · Answer 3 · answered May 12 '16 at 08:49

17

if the tests are not showing in the test explorer you need to install NUnit test adapter :

go to Tools->Extensions and updates ->Online->Visual Studio Gallery->Tools->Testing and select NUnit Test Adapter

answered May 12 '16 at 08:49

Sonja

575
1
6
20

1

then the tests d=should appear in the test explorer. I had the same problem. but only you should wait few mins if there are many tests. You can also uninstall and reinstall NUnit Test Adapter – Sonja Apr 25 '17 at 11:45

score 5 · Answer 4 · answered Dec 22 '17 at 12:41

Visual Studio can change the default processor architecture when it loads. While looking endlessly trying to figure out the issue, I finally figured it out, that it wasn't really Specflow causing the issue.

If you have references that require a special architecture, it will prevent the tests from showing up in the test explorer. Change the architecture to x86 or x64 based on your needs.

Another thing you can do to see the build issues is open the Output window and change the dropdown to Tests during build. It will highlight any information of things taking place during your build.

I felt somebody should mention it just in case.

score 2 · Answer 5 · answered Jul 03 '18 at 11:00

I'm running SpecFlow tests with SpecRunner and had this same problem, a couple of times as a matter of fact. Having tried all of the above suggestions, I found that the only solution to the problem was to uninstall and reinstall the SpecRun NuGet package. Next build, tests present in Test Explorer window as expected.

score 2 · Answer 6 · answered Sep 22 '18 at 08:36

2

In my case the reason why tests weren't discovered were because I was using Resharper build.
As soon as I went to: Resharper -> Options -> Tools -> Build -> General: "Use ReSharper Build"(untick), then all tests were suddenly discovered.

answered Sep 22 '18 at 08:36

HamsterWithPitchfork

750
1
12
21

score 2 · Answer 7 · answered Oct 21 '18 at 10:55

In my case all the approaches above didn't work. My solution: I don't know why, but - I re-installed "Specflow for Visual Studio 2015" in "Tools => Extensions and Updates", then I've created a new feature file (old still didn't work), and this new feature-file works correctly.

Mike · Answer 8 · 2021-02-17T08:20:52.920

For me, I changed from using direct DLL references to using the NuGet references of version 3.1.7.4 of SpecFlow and this solved the problem.

I needed to reference "SpecFlow", "SpecFlow.NUnit" and "SpecFlow.Tools.MsBuild.Generation". and then clicked the "Show All Files" button in Visual Studio to see the code behind file at a sibling level to it associated Feature file (this used to be an associated child file of the feature file in older versions).

I also need to use the "Include In Project" context menu item on the code behind file, for tests to show up in Visual Studios "Test Explorer".

NOTE: I did try to unzip the Specflow required files from the NuGet package and reference them directly in my project to be consistent with other direct references in my project (non-NuGet references) but this doesn't seem to work and you have to use the NuGet reference. I found an closed issue in github, which states that we have to use the Nuget reference to get the tests to work in Test Explorer: https://github.com/techtalk/SpecFlow/issues/1617

score 1 · Answer 9 · answered Jun 27 '19 at 14:59

1

For me, the issue was the TestAssemblyPath in my srprofile file. It didn't match my actual dll name.

answered Jun 27 '19 at 14:59

kevinpo

1,853
19
20

score 0 · Answer 10 · edited May 11 '20 at 07:14

0

I tried installing the Nugget package

SpecFlow.Tools.MsBuild.Generation

with the same version than specflow and now I can see the test in TestExplorer, other ways not works for me.

I already had installed 1 from

Nugget Package Specflow
Specflow.NUnit
Nunit
Nunit3TestAdapter

and the extension for Visual Studio for Specflow a NUnitTestAdapter

edited May 11 '20 at 07:14

Peyman Mohamadpour

17,954
24
89
100

answered May 10 '20 at 22:16

Rose8525

109
6

Built tests are not added to the Visual Studio Test Explorer window

10 Answers10

Linked