specflow

I have several specflow .feature files to test different entities of a web api project. For every entity I have to create a background with all the needed data in my database, but before of all I need to delete all data, and need to delete using web api calls (not by sql query). I'm doing this: Background: Given I make a new request to localhost on port 53364 And the path is api/voipport/deleteAll And the request type is Delete When the request has completed Given I make a new request to localhost on port 53364 And the path is api/loopblockingexception/deleteAll And the request type is Delete

Running SpecRun from command line as part of a Continuous Integration setup, and recently an ignored ( @ignore ) test generated an exit code of 120 when SpecRun completed. Currently, we break the build on any exit code not equal to 0 (universal success indicator!). What does exit code 120 mean exactly? Is it simply "A test was ignored"? or does it imply more? What other values are returned? Sample build output below. We collect all exit codes (currently 1 SpecRun task, so only 1 exit code is collected), and print out to "exit codes" 58> Done. 58> Result: all tests passed (5 ignored) 58> Total:

Is it possible to access the MSTest TestContext from within a SpecFlow (1.7.1) step binding class? In the generated code of a feature file there is a method FeatureSetup which takes the TestContext as an argument but apparently doesn't do anything with it. I found a way to pass parameters to TestContext and then access them from SpecFlow. By adding a [TestClass] which has a TestContext property and marking its AssemblyInit() method as [AssemblyInitialize] so it gets initialized early before runnig the tests and MSTest will be able to populate the TestContext. { [TestClass] public class

How to simply want to input a value in a text box , select the complete text from the text box using "Ctrl+a" , then copy it using "Ctrl + c" and then Paste it in the same box with "Ctrl + v" using Selenium + C#. Arpan Buch [FindsBy(How = How.Id, Using = "search-criteria")] public IWebElement txtProductSearch1 = null public void copypaste(string strCopy) { txtProductSearch1.Click(); txtProductSearch1.Clear(); txtProductSearch1.SendKeys(strCopy); txtProductSearch1.SendKeys(Keys.Control + "a"); //a in smaller case txtProductSearch1.SendKeys(Keys.Control + "c"); // c in smaller case

For acceptance testing I use TeckTalk SpecFlow in Visual Studio 2012. When I run all specflow scenarios, resharper unit test session windows is opened I can see all test results. Like on screen shot below. The question is, when I see failed test (scenario) in some feature file, how can I navigate directly to this feature file from resharper session window to edit it??? It seems to work perfectly well if run via the new VS2012 Test explorer, which on my machine worked automatically from "Run SpecFlow Scenarios" on the project menu. I can only assume Resharper is getting in the way on your

I have written two lines(When's) in my same feature file When user $action1$ $key1$ with $value1$ for $atttributeType_Value$ in $Filename1_SectionId1$ Then abc When user $action2$ $key2$ with $value2$ in $Filename2_SectionId2$ Then def and corresponding step definition in step definition file as [When(@"user (.*) (.*) with (.*) for (.*) in (.*)")] public void abc() { //operation } [When(@"user (.*) (.*) with (.*) in (.*)")] public void def() { //operation } But, its showing up an error as "Multiple match bindings found. Navigating to first match.." When I try to navigate for 1st line its

I have bindings in an external assembly (As per the specflow docs here ) We need this, as we are making a generic library of Step Definitions that can be used in any of our test suites. It works, however some specflow functionality does not appear to work. Namely: All steps are highlighted purple (Indicating that it cannot be matched with a binding) If you select a step and hit F12 or right-click and select "Go To Step Definition", it says it cannot find a matching binding. However, the code runs OK, and if you debug it, you can step from the feature file into the step definition file, so it