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

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.

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.

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));

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

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 solved the issue by upgrading the Serenity Maven Plugin from:

2.0.89

to:

2.1.8

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.

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.