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

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/

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 {

       }

Answer 11 from this Stack Overflow question solved my problem

Apparently you have to run the class containing the test, and not the test itself.

You are able to use csv as it is a direct use txt file. If you want to use excel, need poi dependency which can help you to fetch excel data or create one. dependency groupId org.apache.poi artifactId poi version 3.14

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>

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

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.

Put in the test, in try-catch waiting for the popup. If it will appear - make needed actions, then go to next step, if don't appear - then just go to the next steps. Here is almost same question with good answer: Executing scenario even if one of the step is failed