Hi,
we lately switched to JBehave 3.9.1.
I don't know if it is related, but we face the following weird issue.
we have a class that runs few stories (A, B). In the middle of story A we
suddenly started to see scenarios from story B. (we see it on Junit report
on jenkins).
the original behavior was
Title: Message Title
Mauro Talevi commented on an issue
That was the default story reporter, which is now deprecated in favour
of the story reporter builder.
On 13/05/2014 14:04, Paul Hammant wrote:
Isn't there also useStoryReporter()?
Like so:
public Configuration getConfiguration()
{
return new MostUsefulConfiguration()
.useStoryParser(new Gherk
Isn't there also useStoryReporter()?
Like so:
public Configuration getConfiguration()
{
return new MostUsefulConfiguration()
.useStoryParser(new GherkinStoryParser())
.useStoryControls(
new StoryControls()
.doDryRun(TestConfiguration.getInstance().d
We managed it to integrate log4j logging into the JBehave story reports.
For example you can see in the HTML report all loggings higher than INFO
priority and in the TXT report you see loggings higher than DEBUG priority.
One day I will document that I think.
Title: Message Title
Michael M commented on an issue
