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.
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 Stack: 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()
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.
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..
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?
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.
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?
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