UNINSTALL SPECFLOW 1.8.1 FIRST! SpecFlow integration for Visual Studio 2010 and 2012. Sponsored by TechTalk (http://www.techtalk.at).

(19) Review
Visual Studio
2012, 2010
Download (126,223)
E-mail Twitter del.icio.us Digg Facebook
Add to favorites
Reviews (19)
Q and A (7)
Sign in to write a review
Sort by:

by Roger TCB | October 09 2015

I'm developing using Visual Studio Express 2012 for Web.
I'm following the instructions for installing this but it's invisible: Inside the IDE Extensions & Updates can't see it online even though hundreds of others are there. If I download the specified add-on & try to run it I'm told I have nothing it can install on.

by Ming Zhu | January 14 2014

We are an online classified company. We have over 3,000 functional tests using Specflow with Selenium and API testing tools, and Specflow handles well. It greatly reduced the effort of creating new tests and maintaining tests. Thank you, TechTalk, for making it free.

by kat_tech | November 08 2013

WOW! I just spent 2.5 hours on this! Visual Studio just crashes and reopens ! Why? This may be helpful for someone who installed Flow! Uninstall it!

Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: Rhino.Licensing.LicenseExpiredException
at Rhino.Licensing.AbstractLicenseValidator.HasExistingLicense()
at Rhino.Licensing.AbstractLicenseValidator.LeaseLicenseAgain(System.Object)
at System.Threading.TimerQueueTimer.CallCallbackInContext(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.TimerQueueTimer.CallCallback()
at System.Threading.TimerQueueTimer.Fire()
at System.Threading.TimerQueue.FireNextTimers()
at System.Threading.TimerQueue.AppDomainTimerCallback()

TechTalk SpecFlow Team November 09 2013
| Edit |

From the exception it seems that your Rhino license has been expired. SpecFlow does not use Rhino, so this might be a problem of your setup.

by HSIM | September 01 2013

My first impression is pretty positive. I have yet to learn and try more and deeper. So, it is rather a request than a review. Please do not abandon this prematurely like other tools that were tried. It is very frustrating to lose a tool for which lots of efforts have been made by both the developers of the tool and the users of the tool alike. I hear negative feedback on MS due to many technologies and/or projects abandoned by the company, supporters, and community.

Fortunately, this tool seems very promising. So, please keep improving it so that this can become a reliable add-in for VS for long.

Job well done!

by causas | May 22 2013

by Richard Szalay | May 16 2013

by Vicenç García | April 04 2013

Great tool!

by Bruno Soko | March 26 2013

The tool is awesome! thanks!

by Rafael Leonhardt | February 26 2013

Great tool!

by swati.m | January 29 2013

I have been using this tool as a replacement for cucumber for past one year. Its impressive, easy to follow. Automating Integration tests made easier.

by stensones | December 11 2012

Outstanding tool; a very friction free specification by example.
easy for our developers and easy for our customers.

by Juan Blanco | November 15 2012

by AAKoken | September 10 2012

by TJGLee | September 05 2012

This is a very very good plugin for VS. Started doing bdd development as our ruby team qa liked it and were use to cucumber, have to say this has made our integration testing a lot simpler! we can produce new test routines in minutes. For free software this is amaizing.. good work peeps..

by Mikhail Brinchuk | August 16 2012

by Igor-Moreira | August 15 2012

Não funcionou perfeitamente com o Visual Studio 2012

by Nithin Shenoy | August 10 2012

Fantastic tool. Really changed the way I approached writing test automation.

by marcusoftnet | August 09 2012

Wow... Just Wow.

Took a great tool and made it even better.


by John Katsiotis - djsolid | August 07 2012

Sign in to start a discussion

  • Is this compatible with Specflows external stepAssemblies?
    2 Posts | Last post June 24, 2015
    • Hi there
      We have to distribute our test code across separate product teams, and to support this we have to make available a central 'Core' package.  This contains the base step definition, hooks, exposes resources, and holds common step definitions.
      This all works at runtime, but the plugin does not seem to have visibility of the step definitions in the external assembly.  
      This means that the users have no library/intellisense, so can't create new tests as they have no way of knowing what steps are available (all steps remain purple)
      Is there anything we can do to make the plugin show that the steps are available?
      Many thanks,
    • I'm having the same issue here. 
      Any updates on this?
  • Support for VS2015
    1 Posts | Last post March 24, 2015
    • Any chance of an update for VS2015?
  • Support for VS 2013
    3 Posts | Last post November 26, 2014
    • When we gonna have Specflow supported on VS 2013?
      Appreciate if "Soon" be the answer  :D
    • Soon. ;-)
      I hope we can make an update until end of September.
    • And VS 2015 preview?
  • SpecFlow is crashing within seconds of opening feature
    2 Posts | Last post November 20, 2014
    • Application: devenv.exe
      Framework Version: v4.0.30319
      Description: The process was terminated due to an unhandled exception.
      Exception Info: System.AccessViolationException
         at EnvDTE.ProjectItem.get_Kind()
         at TechTalk.SpecFlow.Vs2010Integration.Utils.VsxHelper.IsPhysicalFile(EnvDTE.ProjectItem)
         at System.Linq.Enumerable+WhereEnumerableIterator`1[[System.__Canon, mscorlib, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089]].MoveNext()
         at System.Linq.Enumerable+<SelectManyIterator>d__14`2[[System.__Canon, mscorlib, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089]].MoveNext()
         at System.Linq.Enumerable+WhereSelectEnumerableIterator`2[[System.__Canon, mscorlib, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089]].MoveNext()
         at System.Collections.Generic.List`1[[System.__Canon, mscorlib, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089]]..ctor(System.Collections.Generic.IEnumerable`1<System.__Canon>)
         at System.Linq.Enumerable.ToList[[System.__Canon, mscorlib, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.Collections.Generic.IEnumerable`1<System.__Canon>)
         at TechTalk.SpecFlow.Vs2010Integration.LanguageService.ProjectFilesTracker`1[[System.__Canon, mscorlib, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089]].InitializeInternal()
         at TechTalk.SpecFlow.Vs2010Integration.LanguageService.BindingFilesTracker.InitializeInternal()
         at TechTalk.SpecFlow.Vs2010Integration.LanguageService.ProjectFilesTracker`1[[System.__Canon, mscorlib, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089]].InitializeInternally()
         at TechTalk.SpecFlow.Vs2010Integration.LanguageService.DelegateTask.Apply()
         at TechTalk.SpecFlow..
    • Note I opened issue #378 on GitHub
  • Visual Studio version support
    1 Posts | Last post August 07, 2013
    • It appears that Specflow can only be installed for Visual Studio Pro, Premium, and Ultimate.  Is there any work around for Test Professional?
  • Specflow 1.9.2 as a nuget package
    2 Posts | Last post May 05, 2013
    • Hi, Could you please tell me why the latest version of specflow (1.9.2) is not avalaible as a nuget package? We use it on a build machine without VisualStudio installed and I don't think we can use vsix..
    • These are two independent components addressing different concerns:
      The NuGet Package provides the SpecFlow runtime API (to be referred from SpecFlow projects), which latest version is 1.9.1.
      The VSIX package provides the SpecFlow Visual Studio integration (feature file editor, project templates), which latest version is 1.9.2.
      You always need the NuGet package in order to use SpecFlow. The VSIX package just improves handling SpecFlow in Visual Studio. Most SpecFlow users use both components.
      The Visual Studio integration is able to handle earlier SpecFlow NuGet runtime versions.
      There is currently no NuGet version 1.9.2 of SpecFlow, as there were no changes in the SpecFlow runtime API, when the updated 1.9.2 SpecFlow VS integration was released.
  • Visual Studio Hangs
    5 Posts | Last post April 23, 2013
    • I'm using VS 2012 and since using specflow I am randomly getting hung in visual studio while editing feature files.  I have to kill the proc in task manager and restart the app. 
      Anyone else experience this?
    • see https://github.com/techtalk/SpecFlow/issues/128
      the issue is fixed, the new release is on the way (published within a week), hold on... :)
    • Awesome Thanks.  After reading through the forum post on github it's the exact issue we have randomly as well.  Thanks for the quick response and congratulations on tracking it down! 
    • Hi,
      I don't see the meny option "Generate Step Definitions" in either VS2010 or VS2012. I have the latest SpecFlow installed. What can be the problem?
      I have tried to reinstall several times.
    • Could it be that Specflow is not yet added to your project?
      When you see curls under your given, when and then keywords, that's probably the case.
      You cann add Specflow by choosing Tools -> Library Package Manager -> Package Manager Console, and then
      PM> Install-Package SpecFlow.NUnit
      For me this worked