Cucumber and Watin for Acceptance testing in Asp.Net MVC

Question

If the business owner/QA are writing/running the Acceptance test against the front end of a Asp.Net Mvc Application, is there a benefit to using SpecFlow/Watin or SpecFlow/Selenium over Cucumber/Watir, besides the "all on one platform" benefit?

Answer 1

The major benefit for me is that Specflow compiles feature file into the unit tests.

I am using NUnit and with this feature I can run my tests written in “classic” style and GivenWhenThen style in one suite. Some things look very ridiculous when I’ve tried to describe them in Gherkin (Specflow):

Scenario: The edit user page should have button Delete
Given I am on the EditUserPage 
When I open ‘MyUser’ for edit
Then I see the Delete button on the EditUserDetailsPage

Imagine, If I have about 20 such UI scenarios in one feature, so who will read all this GivenWhenThen mess?

Sure, I can refine that scenario to make it in one step, but instead of that I am writing a classic unit test:

public void The_edit_user_page_should_have_button_Delete()
{
    EditUserDetailsPage editUser = new EditUserDetailsPage();
    editUser.Invoke(“MyUser”);
    Asset.IsTrue(editUser .btnDelete.Exists, “Button Delete should be there”);
}

Using the Specflow, I can use classic unit tests and features in one test suite because specflow compiles the scenarios into the unit tests