[
https://jira.codehaus.org/browse/JBEHAVE-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-588:
---------------------------------
Affects Version/s: (was: 3.5)
3.4
Fix Version/s: 3.x
> FailingUponPendingSteps only works for normal steps, it does not do as it
> suggests for composite steps
> ------------------------------------------------------------------------------------------------------
>
> Key: JBEHAVE-588
> URL: https://jira.codehaus.org/browse/JBEHAVE-588
> Project: JBehave
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.4
> Reporter: Paul Hammant
> Fix For: 3.x
>
>
> Whereas as mismatching (regex) step text causes PENDING (as expected), then
> subsequent job failure for regular given, when or then steps, this the case
> for composite steps. E.g. the following ...
> {noformat}
> @Given ("This matches just fine")
> @Composite(steps = ["This matches nothing", "Perhaps this matches, perhaps
> it does not"])
> public void unimportantMethodName() { }
> {noformat}
> ... does not cause ultimate build failure.
> Moreover, the step executer continues to the next step rather than marks that
> as NOT PERFORMED as expected. Perhaps the two are related.
--
This message is automatically generated by JIRA.
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
