I wanted to suggest that the JBehave people add such a feature to JBehave. It does not make much sense to me to run it as JUnit test and seeing nearly nothing in the JUnit view but only in the logs. And a good quality of this feature would be more likely.
Besides this, the Codecentric addon is not as I expect it. If a story has given stories then the JUnit view does not show the given stories (which must be executed first) but only the actual story. As ist seems Codecentric does not use the GivenStories as they are inteded by JBehave, because they seem to be using them just to read common data (this is how they consulted a cutomer to do). But okay, here is the Stacktrace for you. Maybe you can fix and improve it: Reports view generated with 0 stories (of which 0 pending) containing 0 scenarios (of which 0 pending) java.lang.RuntimeException: org.jbehave.core.embedder.Embedder$RunningStoriesFailed: Failures in running stories: stories/logout.story: org.jbehave.core.embedder.StoryManager$StoryExecutionFailed: stories/logout.story at de.codecentric.jbehave.junit.monitoring.JUnitReportingRunner.run(JUnitReportingRunner.java:81) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) Caused by: org.jbehave.core.embedder.Embedder$RunningStoriesFailed: Failures in running stories: stories/logout.story: org.jbehave.core.embedder.StoryManager$StoryExecutionFailed: stories/logout.story at org.jbehave.core.embedder.Embedder$ThrowingRunningStoriesFailed.handleFailures(Embedder.java:495) at org.jbehave.core.embedder.Embedder.handleFailures(Embedder.java:224) at org.jbehave.core.embedder.Embedder.runStoriesAsPaths(Embedder.java:205) at de.codecentric.jbehave.junit.monitoring.JUnitReportingRunner.run(JUnitReportingRunner.java:79) ... 6 more 2013/9/27 Robert Hostlowsky <robert.hostlow...@codecentric.de> > Hi Hans, > > thanks for your description. So there is a problem when running this > in the Eclipse junit view, right? > Can you provide a short snapshot, or just the stacktrace from the console > view? > > Thx, Robert > -- > > Robert Hostlowsky | Senior Software Developer | Agile Software Factory > > codecentric AG | Landsberger Straße 302 | 80687 München | Deutschland > www.codecentric.de > > | blog.codecentric.de > | www.meettheexperts.de > | www.more4fi.de > > 2013/9/27 Hans Schwäbli <bugs.need.love....@gmail.com>: > > As it seems some people from Codecentric have written a custom > JUnit-Runner > > for JBehave. > > > > It shows what stories and scenarios are run in the Eclipse JUnit view, > even > > hierarchical. > > > > https://github.com/codecentric/jbehave-junit-runner > > > https://blog.codecentric.de/files/2012/06/JBehave_JUnit_Results_for_Scenarios_and_Steps.png > > > > But it does not seem to work correctly for jbehave-web-3.6 since a > exception > > occurs. > > > > Maybe some talented guy can contribute such an feature to JBehave? > > > > I would contribute it myself, but I don't know the JBehave and JUnit > details > > good enough. > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
