Hi Lance, thanks for your contribution. First off, it seems to be working fine for me, I can't seem the reproduce the problem you mention on the console reporter.
Secondly, there seems to be quite a big overlap between your test running and the AnnotatedPathRunner. The improvement you're looking for is to have the JUnit Description (or child thereof) at the level of the scenario and/or parametrised scenario - aka the example. Can you please create a jira issue to this end attaching your contribution? We can then try to extend the AnnotatedPathRunner based on it. Cheers On 30/06/2011 13:26, [email protected] wrote: > > Hi All, > > I have taken this to a level where I feel it would be best taken on by > a JBehave expert. I have each Story/Scenario/Example showing up as a > separate entry / test in the junit view. > > Please see the screenshot attached > > <<jbehave.JPG>> > > I'm hoping that at least some of the JBehave users / developers agree > that this is a more user friendly way of developing / running JBehave > JUnit tests in the IDE. > > > I have attached the source code for my initial attempt at getting it > working, for some reason the tests are showing as pending after the > first failure occurrs rather than being run. The test case to run is > jbehave.ListTest > > <<jbehave_deeper_junit_integration.zip>> > > Would anyone from the JBehave team like to take this on? > > > Cheers, > Lance. > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email
