[
http://jira.codehaus.org/browse/JBEHAVE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-234:
---------------------------------
Fix Version/s: 3.0
> Improve JUnit integration
> -------------------------
>
> Key: JBEHAVE-234
> URL: http://jira.codehaus.org/browse/JBEHAVE-234
> Project: JBehave
> Issue Type: Improvement
> Reporter: Jonathan Ross
> Fix For: 3.0
>
>
> As a developer using jBehave running in JUnit in Eclipse, I would like to
> easily determine
> 1. how many individual scenarios have passed or failed, and
> 2. which steps failures occur in
> What springs to mind, is to wire each scenario up as separate JUnit TestCase
> (rather than the single 'testScenario()' method). Doing so, I would easily be
> able to drill down to the individually failing scenarios more easily.
> Regarding finding out which step failed, short of writing a fully-fledged
> plug-in, this would be a simple matter of retaining the actual failure
> exception and setting this in JUnit's test result - the failed step should be
> in the stack trace reported by JUnit.
--
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
