specflow

I want to have the following test step class structure: [Binding] public class BaseStep { [Given(@"there is a customer")] public void GivenThereIsACustomer(Table table) { HandleCustomer(table); } protected virtual void HandleCustomer(Table table) { } } [Binding] public class FeatureOneStep : BaseStep { protected override void HandleCustomer(Table table) { // feature one action } [Given(@"feature one specific step")] public void GivenFeatureOneSpecificAction(Table table) { // do something } } [Binding] public class FeatureTwoStep : BaseStep { protected override void HandleCustomer(Table table)

We would like to integrate an automated functional test solution (developed using SpecFlow and Coded UI) in our build server. The project looks like this: the AUT is a WPF application the developers are working with Visual Studio 2010 Professional automation testers joined the project with Visual Studio 2012 Premium (VS Premium is needed for Coded UI tests) Visual Studio 2010 Professional is installed on the build server Jenkins is used a VM is configured for the development and a 2nd VM will be used by the testers Could someone help me with the build-server integration process? Which are the

I'm trying to run multiple Specflow tests in the Test Explorer, but the challenge is I'm unable to run them in the desired order. ex - I have 3 scenarios in my feature files: Login positive Login negative registration positive Currently, they run in random order. I want them to always run in the above order. How can I configure my feature files to make it possible? For NUnit: Tests inside a scenario run in alphabetical order, so if you want to run them in specific order just rename scenarios like Scenario: 1 Login positive Scenario: 2 Login negative Scenario: 3 Registration positive For other

We're trying to implement global hooks on our specflow tests and are not entirely sure how [BeforeScenario] and [AfterScenario] attributed methods work. The way I've seen it done, those attributes are always defined in a class containing specific steps used in a few scenarios. Can they go somewhere so they apply to all scenarios? Or does attributing the methods with [BeforeScenario] and [AfterScenario] cause them to be run for all scenarios, regardless of where they're actually placed? Ben Smith Yes, you can create global BeforeScenario and AfterScenario methods, but in practice I find that

For my SpecFlow tests, I want to setup an individual logging / tracing of the test progress during the execution of tests. E.g. i want to write all passed / failed steps started / ended scenarios started / ended features to the windows event log (in order to synchronize it with event log messages generated by other system components during the test). I tried to use the [BeforeFeature], [BeforeScenario], [BeforeStep] Hooks for doing that, but it turned out that I do not have all the required information within this hooks. E.g. i do not know how to get the current text line of the current step

I would like to add the same line to the start of each one of my SpecFlow tests. This line specifies a list of several scenarios which will change over time, and therefore it is not feasible to maintain this list for every test. For example: Given I have set my site theme to <MyTheme> |Theme Names| |Theme 1 | |Theme 2 | |Theme 3 | |Theme 4 | |Theme 5 | I'd like to have this test repeat for each of the themes. The list of themes is not set in stone, and should be maintained in a single place. So far, I've successfully managed to create a Generator Plugin , and I was planning on using this