How to use reportsViewNotGenerated method of net.serenitybdd.jbehave.embedders.monitors.ReportingEmbedderMonitor class

I could not make it run with using configuredEmbedder() but by adding -Dmetafilter="+working -finished" as goals in my mvn run configurations and using the tags @working for scenarios I'm working with and which I want to run and @finsihed for scenarios I don't want to execute. Still I have to change the run configuration if I want to change the meta tags so it is not very comfortable but still I get what I was looking for.

If you need to continue after a failed step, you should use soft assertions.

The "and etc." you reference probably has some more relevant info. Going by what you have, though, this looks like you have multiple dependencies on guava, and not all of them are the same version. (Note that some of them may be transitive dependencies: those that are included as a dependency by another dependency).

The maven-enforcer-plugin detects when a single library has multiple versions specified, and it breaks the build. If you're just trying to run a quick test, though, you can probably add -Denforcer.skip=true. This is not recommended for long-term use, but only for running your single test.

Long-term, you will ultimately need to use Maven's dependencyManagement to force a specific version of Guava to be used, overriding the version mismatch.

If you are using Maven take a look at Maven Failsafe plugin Rerun Failing Tests feature:

http://maven.apache.org/surefire/maven-failsafe-plugin/examples/rerun-failing-tests.html

I do not know what was wrong but it is working now after restarting my IDE. My IDE was running for a while (more then a week).

My bad, it appears to be a POM.xml configuration issue:

When using Serenity Rest-Assured, the POM.xml cannot contain the standalone Rest-Assured Dependency. Having both Serenity Rest-Assured and the standalone Rest-Assured libraries in the POM.xml will result in the error.

I solved the issue by upgrading the Serenity Maven Plugin from:

2.0.89

to:

2.1.8

This worked to me:

The JBehave API seems to have changed, it seems you now need to add the ScenarioType parameter:

@BeforeScenario(uponType = ScenarioType.ANY)
public void setTheStage() {
    OnStage.setTheStage(new OnlineCast());
}

Source: https://github.com/serenity-bdd/serenity-jbehave/issues/117

You can try importing Spring libraries and create a singleton object for the driver your created. By this you can share the same browser session from anywhere. To have a new browser for the second instance, quit the browser session in the singleton object and redefine it.