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

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

issue #109

Reading the extra comment / improves question, it sounds indeed like an Integration Test.

There are some need Integration Test libraries like JBehave, Serenity, Cucumber, etc which would probably better for setting this up.

With TestNG, you could create 3 tests, where each next test depends on the previous test. See code sample below, from testng dependency test

package com.mkyong.testng.examples.dependency;

import org.testng.annotations.Test;

public class App {

    @Test
    public void method1() {
        System.out.println("This is method 1");
    }

    @Test(dependsOnMethods = { "method1" })
    public void method2() {
        System.out.println("This is method 2");
    }

}

Here the most simple dependency is show. See the sample code for more complex cases, like groups etc. For setting up two test classes each with their own @Factory

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

issue #109

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.

Enter the following property in serenity.properties file

webdriver.base.url = http://en.wiktionary.org

In your page object define the DefaultUrl like this

@DefaultUrl("/wiki/Wiktionary")
public class DictionaryPage extends PageObject {


}

Serenity will construct the complete URL while calling DefaultUrl.

For further reference on all the properties available in serenity.properties please refer link below https://github.com/serenity-bdd/serenity-documentation/blob/master/src/asciidoc/system-props.adoc

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

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

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.

I had the same problem with a similar project. The reason why surefire didn't count the serenity test results was because the POM contained JUnit and TestNG artifacts. The TestNG artifact was added via a parent POM.

After I removed the TestNG dependency the report showed the number of tests executed.