How to use withParameterSetNumber method of net.thucydides.junit.listeners.JUnitStepListenerBuilder class

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

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.

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

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

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

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

You're using the wrong value for parallel. You have to set it to methods or both. Otherwise Surefire will run all tests of your runner class serially.

https://github.com/cucumber/cucumber-jvm/tree/main/cucumber-junit

Cucumber JUnit supports parallel execution of feature files across multiple threads. To enable this with maven set the parallel property to either methods or both.

<build>
    <plugins>
        <plugin>
            <artifactId>maven-surefire-plugin</artifactId>
            <!-- Use 2.22.1 or higher -->
            <version>${maven-surefire-plugin.version}</version>  
            <configuration>
                <parallel>both</parallel>
                <threadCount>4</threadCount>
            </configuration>
        </plugin>
    </plugins>
</build>

Add dependency to pom.xml:

<dependency>
    <groupId>org.junit.platform</groupId>
    <artifactId>junit-platform-engine</artifactId>
    <version>1.2.0</version>
</dependency>

First you have an exclusion for:

    <exclusions>
        <exclusion>
            <groupId>io.cucumber</groupId>
            <artifactId>cucumber-core</artifactId>
        </exclusion>
    </exclusions>

which should explain the "ClassNotFoundException: cucumber.runner.TimeServiceEventBus" error.

Further you have duplicate dependencies. You should really investigate all the warnings that Maven is giving you. And lastly, you are forcing possibly incompatible pieces of Serenity onto itself, by explicitly declaring individual bits of Serenity. Unless you have a particularly good reason for this, you should really avoid that!

In any case, the one simple dependency:

            <dependency>
                    <groupId>net.serenity-bdd</groupId>
                    <artifactId>serenity-cucumber</artifactId>
                    <version>${serenity.version}</version>
            </dependency>

brings in everything you will need: all of Cucumber, all of Selenium, JUnit, and of course all of Serenity.

You can also use:

            <dependency>
                    <groupId>net.serenity-bdd</groupId>
                    <artifactId>serenity-cucumber4</artifactId>
                    <version>${serenity.version}</version>
            </dependency>

note the extra 4 there, if you want to use Cucumber version 4. Although last time I checked (admittedly it has been a while), this was still experimental.

See mvn dependency:tree to make sure.