[
http://jira.codehaus.org/browse/JBEHAVE-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235534#action_235534
]
Mauro Talevi commented on JBEHAVE-338:
--------------------------------------
Brian is quite right - this is not a regression, rather a feature
(JBEHAVE-325).
It is also documented in
http://jbehave.org/reference/stable/migrating-from-2.x.html
The usecase of indented scenarios is quite rare and is outweighted by the
advantage of allowing keyword in comments, titles, tables etc ...
If one wants to keep at all costs tabs/spaces before keywords, a possible
workaround would be writing a pre-parser that strips these tabs/spaces before
passing it to the RegexStoryParser.
> Indented scenarios in stories was possible in JB2 but after upgrade failed in
> JB3
> ---------------------------------------------------------------------------------
>
> Key: JBEHAVE-338
> URL: http://jira.codehaus.org/browse/JBEHAVE-338
> Project: JBehave
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.0
> Environment: Windows
> Reporter: Paul Hammant
> Priority: Minor
>
> A client had indented JB scenarios (tabs and/or spaces) in the .scenario
> files. When upgraded to JB3, and everything else was working for the renamed
> .story files. the scenarios were not being executed. It seems regex made no
> match.
> We had breakpoints in place so we could see the BeforeScenario being invoked,
> but none of the steps. When we removed the left-whitespace, it worked.
--
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
