[jbehave-dev] [jira] (JBEHAVE-1070) Loose StepType

[Alberto Scotto (JIRA)]

Title: Message Title

Alberto Scotto created an issue   JBehave / JBEHAVE-1070 Loose StepType Issue Type: Improvement Assignee: Unassigned Components: Core Created: 11/Mar/15 3:33 PM Priority: Major Reporter: Alberto Scotto Hi, I've recently started working with jbehave, and I am noticing duplication when a step method can be more than one StepType, e.g.: @When("the cart is empty") @Then("the cart is empty") public void cartIsEmpty() {} An easy workaround could be to support the following syntax @When("the cart is empty") @Then public void cartIsEmpty() {} i.e. in case a method has multiple StepType annotations, only one value needs to be not empty. But I think there's a more elegant solution. The Cucumber Book says something interesting about this: Given, When, Then Are the Same. It doesn’t actually matter which of the three methods you use to register a step definition, because Cucumber ignores the keyword when matching a step. Under the hood, all of the keyword methods are aliases for Cucumber:: RbDsl#register_rb_step_definition. The keywords are really just there for extra documentation to help you express the intent of each step or step definition. This means that, whether it was created with the method Given, When, or Then, a step definition will match any Gherkin step as long as the regular _expression_ matches the main text of the step I like this concept. At the end of the day, the difference between a Given and a Then is just a matter of meaning. And of position (i.e. given before then), at most. So what about going a little bit farther and defining a generic Step annotation? @Step("the cart is empty") public void cartIsEmpty() {} There is a problem, though, as I think this would break JBEHAVE-196 . But then, as far as I understand, the ultimate solution would be to support regexes, wouldn't it? Which is another feature that would be a very-nice-to-have, I think. Thanks Add Comment   This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email