How to use testRunFinished method of net.thucydides.junit.listeners.TestCountListener class

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.

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.

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.

The problem is naming convention of properties file, Since you named it as application-QA1.properties it becomes profiles specific properties file Profile-specific properties and you can load those properties by making profile active in application.properties like here

spring.profiles.active=QA1

Or through command line

java -jar myproject.jar --spring.profiles.active=QA1

And another information, value in @Component annotation indicates the bean name

he value may indicate a suggestion for a logical component name, to be turned into a Spring bean in case of an autodetected component.

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
  }
}

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

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"

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());

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/