How to use scenarioWeightFor method of net.serenitybdd.cucumber.suiteslicing.MultiRunTestStatistics class

By principle, Cucumber doesn't supports data from external files. Instead it encourages to provide examples with scenario. However there are few non standard way available with cucumber to use examples from the external file. One of them, you can refer in grasshopper's post.

Another alternate is using gherkin with QAF which provides lots of features inbuilt data-providers including XML/CSV/JSON/EXCEL/DB. Here is the step-by-step-tutorial to start with.

See https://github.com/serenity-bdd/serenity-core/#cucumber-4. I expect Serenity will only work with JUnit 5 in vintage mode.

Looks like you are indirectly running Serenity through the junit-vintage-engine. When executed this way, parallel execution is simply not supported.

To be exact you are running your tests through Surefire -> JUnit 5 -> JUnit Vintage -> JUnit 4 -> Serenity -> Cucumber.

You'd have to wait for JUnit Vintage to support parallel execution or get rid of JUnit 5 from your depencies so Surefire can run JUnit 4 directly.

However given that you are also using Spring you may not be able to get rid of JUnit 5.

You could ask Serenity to support JUnit 5 but I suspect they will be unable too. They have never bothered to contribute the extension points they'd need upstream. Instead they have hacked their stuff into Cucumber.

If you are trying to run an After hook after each scenario tagged with "@tag1" in your example, you should mark the After hook with "@tag1". For more information on tagged hooks, please refer to the Cucumber documentation.

Below are the steps from John Ferguson Smart' blog, author of Serenity-BDD (considering that you have installed Cucumber for Java plugin).

Running Cucumber with Serenity feature files directly from IntelliJ:

IntelliJ provides excellent integrated support for Cucumber feature files. You can even run features simply by right-clicking on the feature file. But this won’t work when you are using Cucumber with Serenity, as Serenity needs to instrument the feature file before execution. Fortunately, this is easy to fix. Here’s how:

• Click on the feature file you want to run
• In the Run menu Select Run…
• In the contextual menu, select the feature, then “Edit…”
• You should now see the ‘Edit Configuration Settings’ window. Set the main class to ‘net.serenitybdd.cucumber.cli.Main’
• Change the Glue field to the root package of your project (or of your step definitions)
• Click Apply

Now you can run your feature directly by right-clicking on the feature file.

P.S. Not all versions of Cucumber for Java plugin works correctly, especially when you have just updated IntelliJ IDEA to the latest version. I can confirm that next setup works correctly:

• IntelliJ IDEA 2018.2.3 (Community version);
• Cucumber for Java plugion version 182.3934;
• net.serenity-bdd:serenity-core:2.0.6;
• net.serenity-bdd:serenity-cucumber:1.9.18

Check https://github.com/temyers/cucumber-jvm-parallel-plugin There is stated:

As of cucumber-jvm:4.0.0 parallel execution is supported natively by cucumber. As such, upgrading to Cucumber 4.0.0 is recommended and this plugin is no longer maintained.

So consider leave cucumber-jvm-parallel-plugin

It looks like you have in your pom.xml something like

<tags>"~@ignore"</tags>

try to change it to

    <tags>
      <tag>~@ignore</tag>
    </tags>

BTW proper new style is now not @ignore check https://github.com/cucumber/cucumber/tree/master/tag-expressions#migrating-from-old-style-tags

İ have solved the issue through making the constructor in the step definition file empty, defining the driver variable as static in the hook definition file and instantiating as a class object in the step definition file where İ called the getDriver method.

İt seems that serenity needs an empty constructor in the step definition file.

You're defining your profiles in the wrong place. The correct place is directly under project:

<project>
    ...
    <profiles>

and then the plugin-configuration for that profile:

<project>
    ...
    <profiles>
    ...
      <build>
          <plugins>
             ....

That means you'll have to define the plugins mutliple times (per profile). The profile-information in configuration has to be removed.

I think this is a Chromedriver bug, as indicated by the stack trace.