How to use restarted method of net.serenitybdd.jbehave.SerenityReporter class

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.

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.

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

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

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

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

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

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.

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

2.0.89

to:

2.1.8

WebdriverIO is a JavaScript / nodejs implementation of the (Selenium 2.0) WebDriver API - one of many (Selendroid, Protractor, etc.) As the specification says:

WebDriver is a remote control interface that enables introspection and control of user agents. It provides a platform- and language-neutral wire protocol as a way for out-of-process programs to remotely instruct the behaviour of web browsers.

If you use Java, you'll use the Java implementation of WebDriver. Which language, and which implementation you choose, is up to you, your skills, and the skill of your team.

Though I very much doubt that WebdriverIO is "not mature enough". WebDriver is a fine spec, with a number of powerful implementations, but it is very frequently misused. Certainly as far as newbies go, a very large proportion of "random" failures are completely avoidable race conditions within their test code.