How to use usingThreads 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

Serenity has this feature now

18. Running Serenity tests in parallel batches

http://thucydides.info/docs/serenity-staging/#_running_serenity_tests_in_parallel_batches

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.

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.

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

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

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.

Add dependency to pom.xml:

<dependency>
    <groupId>org.junit.platform</groupId>
    <artifactId>junit-platform-engine</artifactId>
    <version>1.2.0</version>
</dependency>

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

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