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

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.

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

2.0.89

to:

2.1.8

It would seem that Serenity will pick up on steps brought in through dependencies all on its own, so no need for anything fancy.

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.

A issue has been raised (including quick fix) with the bdd serenity-jbehave version 1.8.0 and higher:

issue #109

You need to add an instance of ContextStoryReporter to your configuration:

configuration.storyReporterBuilder().withReporters(new ContextStoryReporter(context));

I resolved the above issue and I managed to generate the report in Jenkins. I did the following: 1)Changed the versions in properties in pom.xml file to the following:

serenity.version-1.2.4, serenity.maven.version-1.2.4, serenity.jbehave.version-1.1.0, a-maven-plugin.version=4.3.1

2)In Jenkins post build config, I changed the following:

<alwayslinktolastbuild> true </alwayslinktolastbuild> <keepAll>true</KeepAll> <reportDir>${WORKSPACE}/target/site/serenity</reportDir>

Hope this helps! Thanks! :)

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 found the answer. The driver confguration used by the framework is held in the serenity.properties file associated with the project.