[jbehave-dev] [jira] (JBEHAVE-1070) Loose step matching, not based on StepType

2015-03-12 Thread Mauro Talevi (JIRA) 
Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: Loose step matching, not based on StepType 










While it's true that this constraint is strictly speaking not needed, it is nonetheless useful as it forces scenario writers not to be lazy and think about the syntax and how to word the steps. It is rather unlikely that steps of different types have exactly the same syntax. One could argue that it's a smell. 
That said, there are situations where that may happen. In this case it may be worth introducing an ANY value in the StepType enum (rather than dropping the step type). 
Having an annotation @Step(type=ANY) could be a good suggestion. We could then also have @Step(type=GIVEN) as an alias to @Given, etc ... 












   

 Add Comment











 













 JBehave /  JBEHAVE-1070



  Loose step matching, not based on StepType 







 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.:   {code}  @Given("the cart is empty")  @When("the cart is empty")  public void cartIsEmpty() {}  {code}   An easy (?) workaround could be to support the following syntax   {code}  @Given("the cart is empty")  @When  p...















 This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)

[jbehave-dev] [jira] (JBEHAVE-833) Provide a configurable timeout value for each story running time

2015-03-12 Thread Mauro Talevi (JIRA) 
Title: Message Title










 

 Mauro Talevi commented on an issue











 






  Re: Provide a configurable timeout value for each story running time 










You're mixing two very different concerns here, configuration and monitoring. 
What matters is whether the path of the story we're running matches the regex patterns provided in the CSV of story timeouts. 
I'm looking into simplify your solution. 












   

 Add Comment











 













 JBehave /  JBEHAVE-833



  Provide a configurable timeout value for each story running time 







 When running stories that may take a bit longer, e.g. web tests, a timeout value for each story would be useful as opposed to a timeout for all stories together.  















 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