List of Classes and Methods of net.serenitybdd.jbehave.service package of Serenity jBehave Framework

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.

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

2.0.89

to:

2.1.8

We found our issue was that in the Scenario line some of our test cases looked like

Scenario: XXX-#9056: Change password to special characters

Instead of

Scenario: XXX- 9056: Change password to special characters

So having the pound symbol(#) on the line with Scenario was messing it up. It doesn't matter if it is under the meta tag. Now none of the skipped test are showing in the report.

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

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.

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.

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 do not know what was wrong but it is working now after restarting my IDE. My IDE was running for a while (more then a week).