How to use ThucydidesJUnitModule class of net.thucydides.junit.guice package

Have you tried upgrading the version of IE Driver to 2.53.0?

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

Actually Serenity provides another runner - SerenityParameterizedRunner which seems to have the same features as JUnit's Parameterized.

It seems I'm using Cucumber with Serenity and the Cucumber team is not currently supporting JUnit TestRules for philosophical reasons. Here's hoping they change their mind :)

See https://github.com/cucumber/cucumber-jvm/issues/894

1. go to your repo location and check if the jar is properly downloaded.
2. unpack your WAR and check if the jar is actually available in it.
3. althoug your maven dependency looks fine, but just try using this: 
    <dependency>
        <groupId>com.google.code.gson</groupId>
        <artifactId>gson</artifactId>
        <version>2.3</version>
    </dependency>
4. Make sure you do a mvn clean:install -P from command prompt location of the project.
5. I tried with the same dependency and it works fine with JBOSS too.

You can use tagging for that purpose. Information about that feature can be found in Serenity BDD official documentation.

Just a short excerpt, tags are added to jUnit tests using WithTag annotation. The following will add a tag of type feature (this is a default Serenity type) with name Reporting:

@WithTag(type="feature", name="Reporting")

Then you can run tests with this tag with jUnit like this:

mvn clean verify -Dtags="feature:Reporting"

The issue is simply because you have defined the maven-failsafe-plugin in pluginManagement only.

The usual way is to define the version in pluginManagement while the binding has to be done in build area.

  <build>
    <pluginManagement>
      <plugins>
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-failsafe-plugin</artifactId>
          <version>3.0.0-M7</version>
        </plugin>
      </plugins>
    </pluginManagement>
    <plugins>
      <plugin>
        <artifactId>maven-failsafe-plugin</artifactId>
        <executions>
          <execution>
            <goals>
              <goal>integration-test</goal>
              <goal>verify</goal>
            </goals>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>

I also recommend to upgrade your used plugins which means define newer versions of all used plugin in pluginManagement.

Furthermore you should not define a configuration for maven-surefire-plugin:

<configuration>
  <skip>true</skip>
</configuration>

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.

This link should help, do not forget to give your definitions in glue section of the configuration.

https://johnfergusonsmart.com/running-cucumber-serenity-feature-files-directly-intellij/