How to use shouldResetStepLibraries method of net.serenitybdd.junit.runners.TestConfiguration class

You can have your own runner in serenity and instantiate driver with your desired capabilities for it. By doing so you can configure and redirect logs.

@RunWith(CucumberWithSerenity.class)
@CucumberOptions(
        plugin = {"pretty"},
        features = "<feature file path>",
        glue = {"<steps path as comma separated values"}
)
public class MyRunner {

       }

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.

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"

You can set priority in this way

        @Test(priority = 1,alwaysRun = true)
        public void rentalhomesHomePage() throws InterruptedException {
            //Your test case

        }

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

If you need to continue after a failed step, you should use soft assertions.

Did you try using driver.quit() after running your feature file to close the session?

maven-failsafe-plugin has no notion of "packages". The notion of "suites" is related to junit4 Suite.

To solve my problem above, I did the following:

In each "features.area" I created a "TestSuiteStub":

import org.junit.runner.RunWith;
import org.junit.runners.Suite;

/**
 * This will be processed by groovy-maven-plugin.
 */
@RunWith(Suite.class)
@Suite.SuiteClasses({
/* add test Stories after this ANCHOR */
})
public class TestSuiteStub {
    /* Suite holder */
}

I then used the groovy-maven-plugin with execute goal and the following script:

// find all TestSuiteStub.java
new File("${project.build.testSourceDirectory}/features").  // exploits the "complication" in Maven interpolation and GStrings
  traverse(type: groovy.io.FileType.FILES, nameFilter: ~/TestSuiteStub\.java/) { stub ->
    println 'Using: ' + stub

    // in the same dir as TestSuiteStub.java, find all *Story.java
    def stories = new StringBuilder()
    new File(stub.parent).
      eachFileMatch(groovy.io.FileType.FILES, ~/.*Story\.java/) { story ->
        stories.append story.name.replace('java', 'class')
        stories.append ', ' // will leave a comma at end of list, but javac seems to be ok with that
      }
    println 'Found: ' + stories

    // write out TestSuite.java
    def suite = new File(stub.parent + '/TestSuite.java')
    suite.delete()
    println 'Writing: ' + suite
    stub.eachLine() { line ->

      if(line.contains('Stub'))
        suite.append line.replace('TestSuiteStub', 'TestSuite') + System.getProperty('line.separator')
      else
        suite.append line + System.getProperty('line.separator')

      if(line.contains('ANCHOR'))
        suite.append stories + System.getProperty('line.separator')
    }
  }

This will process each of the TestSuiteStub and generate a TestSuite. So after running this (you can use mvn test-compile to run this, without running your tests), I have something like:

src/test/java
+-features.areaA
| +-SomeStory.java
| +-AnotherStory.java
| ...
| +-TestSuiteStub.java
| +-TestSuite.java
+-features.areaB
| +-DifferentStory.java
| +-OtherStory.java
| ...
| +-TestSuiteStub.java
| +-TestSuite.java
...

where the first TestSuite will look something like:

import org.junit.runner.RunWith;
import org.junit.runners.Suite;

/**
 * This class will be processed by groovy-maven-plugin.
 */
@RunWith(Suite.class)
@Suite.SuiteClasses({
/* add test Stories after this ANCHOR */
SomeStory.class, AnotherStory.class,
})
public class TestSuite {
    /* Suite holder */
}

To make maven-failsafe-plugin pick this up, I configured it like this:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-failsafe-plugin</artifactId>
  <version>${failsafe.plugin.version}</version>
  <configuration>
    <includes>
      <include>features.*.*Suite</include>
    </includes>
    <parallel>suites</parallel>
    <threadCountSuites>4</threadCountSuites>
  </configuration>
  <executions>
    <execution>
      <goals>
        <goal>integration-test</goal>
        <goal>verify</goal>
      </goals>
    </execution>
  </executions>
</plugin>

Lastly I also added *Suite.java to my .gitignore.