How to use useSystemProperties method of net.serenitybdd.jbehave.embedders.ExtendedEmbedder 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! :)

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

issue #109

I found the answer. The driver confguration used by the framework is held in the serenity.properties file associated with the project.

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

See if reverting to previous version of jbehave helps . There seems to be a bug with the 4.0.4 . See this link https://groups.google.com/forum/#!topic/jbehave-dev/7OxwmOXZPVk

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 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.

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

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.