Jbehave-junit-runner incorrectly shows scenarios being executed when mata keywords applied in Jbehave 4 version about jbehave-junit-runner

[falkoner]

@britter Any luck? Please let me know if I can help in any way. Though with update of IntelliJ to 15 (and the change in JUnit reporting results there) it all become way more broken for me.

[falkoner]

I guess we better downgrade to Jbehave core 3.10.0 or 3.9.5 meanwhile... Any ETA on this fix?

[britter]

@falkoner is this a problem with jbehave-junit-runner or with jjbehave itself?

[falkoner]

My understanding is that it's problem on jbehave-junit-runner side. Specifically in area of compatibility with Jbehave 4 branch. As result we downgraded Jbehave used in project to 3.10 from 4.0.1 and it works fine there now.

[britter]

Okay, I'll need time to investigate.

[britter]

@falkoner honestly, I'm not working on this project anymore. If you need a fix, you'll have to supply a PR with accompanying test cases. Sorry!

[Guito]

Doing a currentScenario.getChildren().clear() just before notifier.fireTestFailure(new Failure(currentScenario, new AssertionError("scenario failed!"))); in JUnitSecenarioReporter.afterScenario makes the result look a bit better. It's not perfect but at least it's possible to work with it.

[valfirst]

@falkoner, @Guito, new version is released:

<dependency>
    <groupId>com.github.valfirst</groupId>
    <artifactId>jbehave-junit-runner</artifactId>
    <version>2.0.0</version>
</dependency>

It's based on JBehave 4.1.1. Have you had a chance to try it?

[cliviu]

@valfirst , is the new version already in mavencentral ?

[valfirst]

@cliviu , yes, it's already published, please, pay attention to the changed groupId: http://repo1.maven.org/maven2/com/github/valfirst/jbehave-junit-runner/2.0.0/

[cliviu]

ok, so there is also package name change...
Are there any known issues of the old version (1.2.0) with JBehave 4.1.1 ? We have a problem with the After methods of the lifecycle ... see also : serenity-bdd/serenity-core#924
I will add this stacktrace also :
issue924.txt

[valfirst]

@cliviu , not sure if any matches your case, try to search: https://github.com/valfirst/jbehave-junit-runner/issues?utf8=%E2%9C%93&q=lifecycle. Is there any way to reproduce the issue without Serenity?

[cliviu]

ok, @valfirst, thanks, I will take a look