Hello Andreas,
If this becomes a part of JBehave I would share the scenario, but since I
don't intend to use it (because of the reasons I wrote earlier), I cannot
do that. I work in the financial industry and must be very careful what I
share (which means spend extra time to be sure that it
Hi Hans,
it would have been perfectly sufficient to say if you had an empty examples
table in your scenario that produced that error.
Thanks,
Andreas
2013/10/4 Hans Schwäbli bugs.need.love@gmail.com
Hello Andreas,
If this becomes a part of JBehave I would share the scenario, but since
I think I have no empty example table. My example tables are not empty.
It works as expected without that JUnitReportRunner. Only with
JUnitReportRunner I get a NPE.
2013/10/4 Andreas Ebbert-Karroum andreas.ebbert-karr...@codecentric.de
Hi Hans,
it would have been perfectly sufficient to
Hello Andreas,
thank you, this works.
I had used JUnitReportingRunner.recommandedControls(configuredEmbedder())
in the beginning, but had a StackOverflowError.
Now I discovered that I have misplaced this code line.
But I get another error now:
java.lang.NullPointerException
at
Hi Hans,
do you mind sharing the scenario for which you get the NPE? A wild guess:
You have an empty examples table in that scenario. The jbehave-junit-runner
usually works fine for valid scenarios and stories. But, there may be bugs,
in case you discover one, it'd be extremely nice, if you raise
Sorry for a bit of off topic, but jbehave-junit-runner is indeed great
addition for running JBehave tests and I'd vote for inclusion of it into
standard package if it's proper place to do so. The only thing I'd love to
see there now is ability to go to the step candidate definition by click in
the
Hi Hans,
the problem with the given story is not that I didn't want to provide more
details, but that JBehave is not sending any events about executed given
stories. At least is that what I think what happened, I have not worked on
the jbehave-junit-runner for more than a year now.
Can you
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
