Given / When / Then steps in scenario files should be underlined when action steps are not matched.

User should be able to ctrl-click on Given / When / Then steps and be taken to the matching action step.

Scenario steps should be registered for auto-completion and intellisense within visual studio.

Hi Team,
I'm looking for excel based data driven support from BDD tools. Do you provide the feature to utilize the excel data as parameterization?

Thanks,
Palani

Even before "BeforeRun", which makes impossible any context preparation before running scenario with that background.

The table feature is poorly generated as html with the xslt, it would be nice if this feature could be handled in a similar way as examples.

When i use NBehave.Narrator.Framework.BeforeScenario the method is executed, but not when i use NBehave.Narrator.Framework.Hooks.BeforeScenario.

This is via command runner.

Users should be able to view all features / scenarios in the solution from a single place.

I have 2 features and steps classes:

Product.feature   ProductSteps.cs
Sku.feature       SkuSteps.cs

The scenarios are similar:

Scenario: product
  Given a list of products:
       ....
  When my logic is applied
  Then should assert

Scenario: sku
  Given a list of skus:
       ....
  When my logic is applied
  Then should assert

When i run the Sku.feature it works on steps defined in ProductSteps.cs for some reason.
When i changed the When and Then clauses to be different it works as expected.

Is it a bug or a feature? In any case i think the relationship between feature and steps should be stronger.
I was assuming the engine finds the steps class by its name (feature name + "Steps").

When installing the NBehave Nuget package into a .NET Core app I get the following error:

Package nbehave 0.6.2 is not compatible with netcoreapp1.0.

In the 'Getting started' document, you should include a complete example of running the console runner. Alternatively improve your parser so that it gives meaningful error messages back; instead of the same error message every time.

I am trying to run NBehave-Console.exe to generate test stubs from Gherkin. With this command run from the command line.

NBehave-Console.exe /sf=ViewPremiumByApoGAdmin.feature /codegen

In reply all I ever get is: "fatal error: invalid arguments"

==================================================================
Contents of the file : ViewPremiumByApoGAdmin.feature

Feature: ViewPremiumByApoGAdmin
# New Premium preference, is viewable by ApoGAdmin
In Order To: View all settings
As an ApoGAdmin
I Want To View Premium setting

Scenario: ApoGAdminCanViewPremium
# _1 ApoGAdmin user can view Premium Setting
Given I am an ApoGAdmin
When I Go to Premium
Then I can view Premium setting

I've tried it with and without the comment lines.

Hello,

I have a situation when I need to support big amount of NBehave tests. They are blocking me from updating NUnit for the project.

Please review update of NBehave for NUnit3 support:
#17

Thanks.

For instance

Given a scenario
  When there's one when clause
    And there's another when clause
  Then should check execute both clauses
    And do additional checks

This gives a more granular control, i.e. can create smaller steps and combine them.

I have the following MSbuild targets set up:

If I run GenerateAcceptanceReport target, I get the following error:

C:\Users\vadimk\Documents\BDD\Courseware\BDDTests\BDDTests.csproj(82,5): error
MSB3703: Unable to execute transformation. The process cannot access the file '
C:\Users\vadimk\Documents\BDD\Courseware\BDDTests\bin\Debug\nbehave.results.xml
' because it is being used by another process.

The acceptance tests are run, but the report generation fails. However, if I replace the NBehave call with an Exec call directly to the console, everything works fine. It also works fine if I remove the DependsOnTargets qualification and run them one after the other

Test that shows the bug.
http://code.google.com/r/yads12-nbehave/source/detail?r=fb718ad3970d66e49bf7b0c15b6fda804e730ae9

Requiring exactly one specific version of nunit seems very restrictive. Please could you consider at least allowing point releases.

Matching action steps should be generated for scenerios with missing actions. This could be automatic or using a shortcut / icon.

As a developer
I want to put breakpoint(s) in feature files
So that I can debug a feature/scenario/step