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

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

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.

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.

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

issue #109

Dev of Karate here. I guess you mean the cucumber-reports-plugin.

First: I have never experimented with rendering links, but it looks doable, for e.g refer to this thread: https://github.com/damianszczepanik/cucumber-reporting/issues/610

Second: Karate has enhanced cucumber tags so that name-value-pairs are supported, so even within a test you would be able to grab the value of a tag, here is an example: tags.feature.

In current state of Karate you can certainly get the value of the tag and generate a hyperlink. Rendering a hyperlink into the HTML report may need some digging.

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.

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

2.0.89

to:

2.1.8