How to use navigatorViewGenerationFailed method of net.serenitybdd.jbehave.embedders.monitors.CompositeEmbedderMonitor class

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.

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

issue #109

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

Fail at end should work in your scenario.

Basic Def from Maven Specs :

--fail-at-end - if a particular module build fails, continue the rest of the reactor
           and report all failed modules at the end instead .

You can do following in build.gradle, so when ever you run

task runSpecificRunner(type: Test) {

    include '**/**YOURRunnerName.class'
}

Then run ./gradlew runSpecificRunner aggregate, you will see only that specific runner will be executed.

You can use Meta: to tag stories/scenarios. This is useful if you want to run just subset of stories/scenarios or skip some of them. Example:

Meta: @sometag

Scenario: some scenario
Given something 

Then you can use meta filtering and story mapping to include/exclude scenarios marked with certain tags.

You can change story file names so their lexicographical order will match order you want them to execute:

1_aaa.story  
2_bbb.story
3_ccc.story

or create separate folders:

a/aaa.story
a/bbb.story
c/ccc.story

There is more nice solution in case when you need some story to execute before another one, GivenStories: clause:

GivenStories: aaa.story

Scenario: requires aaa to run
Given something

This will first execute aaa.story then this story. You can specify several stories in GivenStories.

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

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

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 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! :)