[ 
http://jira.codehaus.org/browse/JBEHAVE-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mauro Talevi updated JBEHAVE-278:
---------------------------------

    Fix Version/s: 3.0

> 'And' Step (AndStep) ignores CandidateStep step                               
>                                                                               
>                                                               type
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBEHAVE-278
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-278
>             Project: JBehave
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.5.1
>            Reporter: Tim Moore
>            Assignee: Mauro Talevi
>             Fix For: 2.5.2, 3.0
>
>
> On http://jbehave.org/reference/latest/concepts.html it states:
> "A step starting with And assumes the same meaning of the previous step"
> but this clearly isn't the case in practise, nor does it even require any 
> preceeding step type to be defined. For example with:
>                                                                               
>            
> public class Steps extends org.jbehave.scenario.steps.Steps {
>   @When("the wind blows")
>   public void theWindBlows() { System.err.println("when it blows then boom"); 
> }
>   @Given("the wind blows")
>   public void theWindBlows2() { System.err.println("given it blows then 
> boom"); }
> }
>                                                                               
>      
> Scenario: Test
>   And the wind blows                                                          
>            
> Given the wind blows                                                          
>              
>   And the wind blows
>  When the wind blows
>   And the wind blows
> Outputs:
>                                                                               
>          
> when it blows then boom
> given it blows then boom
> when it blows then boom
> when it blows then boom
> when it blows then boom
> Obviously you wouldn't intend to start your scenario with an AndStep, but 
> it's easy enough to get there (or produce one of the other problems) if you 
> are copying/editing scenarios. I think it would be better if AndSteps assume 
> the meaning of the previous step, as intended(?) according to the web 
> documentation.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to