How to use countTestMethods method of net.serenitybdd.junit.finder.TestFinder class

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 also configure it in serenity.conf file

So something like that;

# Remote
webdriver {
  driver = remote
  remote {
      url="http://localhost:4445/wd/hub"
      driver=chrome
  }
}

If you are using Maven take a look at Maven Failsafe plugin Rerun Failing Tests feature:

http://maven.apache.org/surefire/maven-failsafe-plugin/examples/rerun-failing-tests.html

I had the same problem with a similar project. The reason why surefire didn't count the serenity test results was because the POM contained JUnit and TestNG artifacts. The TestNG artifact was added via a parent POM.

After I removed the TestNG dependency the report showed the number of tests executed.

JDelorean the reason as far as i know is that alert has been popped up before selenium code reacted to the alert code. Hence its wise to add some delay in between the alert code. Something like i did as follows

@Test public void receiptDateFieldIncorrectDateFormat() {

    page.open();

    steps.inputIntoReceiptDateField("99999999");

    steps.clickSubmitButton();

Thread.sleep(3000);

    String firstMsg = page.getAlert().getText();

    page.getAlert().accept();

Thread.sleep(3000);
    String secondMsg = page.getAlert().getText();

    page.getAlert().accept();

    Assert.assertEquals("The year is invalid.", firstMsg);

    Assert.assertEquals("Invalid Receipt Date format.", secondMsg);

}

or you can use something like

> WebDriverWait wait = new WebDriverWait(driver, 15);  
> wait.until(ExpectedConditions.alertIsPresent());

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

Unfortunately Serenity is not supported by basic JUnit 5 so I had to use JUnit 5 Vintage only. It can run JUnit 4 tests. It works now.

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

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