Serenity jBehave

Serenity has this feature now

18. Running Serenity tests in parallel batches

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

It would seem that Serenity will pick up on steps brought in through dependencies all on its own, so no need for anything fancy.

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.

Fail at end should work in your scenario.

Basic Def from Maven Specs :

--fail-at-end - if a particular module build fails, continue the rest of the reactor
           and report all failed modules at the end instead .

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.

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 resolved the above issue and I managed to generate the report in Jenkins. I did the following: 1)Changed the versions in properties in pom.xml file to the following:

serenity.version-1.2.4, serenity.maven.version-1.2.4, serenity.jbehave.version-1.1.0, a-maven-plugin.version=4.3.1

2)In Jenkins post build config, I changed the following:

<alwayslinktolastbuild> true </alwayslinktolastbuild> <keepAll>true</KeepAll> <reportDir>${WORKSPACE}/target/site/serenity</reportDir>

Hope this helps! Thanks! :)

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

You can try importing Spring libraries and create a singleton object for the driver your created. By this you can share the same browser session from anywhere. To have a new browser for the second instance, quit the browser session in the singleton object and redefine it.