How to use FailureDetectingStepListener class of net.serenitybdd.junit.runners package

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 issue is simply because you have defined the maven-failsafe-plugin in pluginManagement only.

The usual way is to define the version in pluginManagement while the binding has to be done in build area.

  <build>
    <pluginManagement>
      <plugins>
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-failsafe-plugin</artifactId>
          <version>3.0.0-M7</version>
        </plugin>
      </plugins>
    </pluginManagement>
    <plugins>
      <plugin>
        <artifactId>maven-failsafe-plugin</artifactId>
        <executions>
          <execution>
            <goals>
              <goal>integration-test</goal>
              <goal>verify</goal>
            </goals>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>

I also recommend to upgrade your used plugins which means define newer versions of all used plugin in pluginManagement.

Furthermore you should not define a configuration for maven-surefire-plugin:

<configuration>
  <skip>true</skip>
</configuration>

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

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

Just confirm first that your using supported surefire and junit version. For more details refer https://maven.apache.org/surefire/maven-surefire-plugin/examples/single-test.html

In case your using maven failsafe plugin then the syntax will vary little bit. Something like this

mvn -Dit.test=ITCircle#test* verify

Refer https://maven.apache.org/surefire/maven-failsafe-plugin/examples/single-test.html for more details.

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

Add dependency to pom.xml:

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

If this is like the popups that I've dealt with they work like this:

1. Customer comes to site and the site checks for the existence of a cookie. If that cookie exists, the popup is never launched (ideal state). If that cookie does NOT exist (typical state), after a specified period of time a popup appears.
2. Customer dismisses the popup and a cookie is created with an expiration time
3. Once that expiration time passes, the cookie expires and the popup will fire again

You need to do some investigation and find the cookie that is created once the popup is dismissed. Clear your cache, browse to the site, and note all the cookies that exist. Wait for the popup and dismiss it. Now find the cookie that was just created and examine it. This is the cookie you need to create. There are a lot of tutorials on creating cookies. It's pretty straightforward.

Once you learn how to create the cookie, you add it to your script as described below:

1. Navigate to some page on the domain that you know doesn't exist, e.g. www.domain.com/some404page. We do this because it won't trigger the popup countdown and we need to be on the domain to create the cookie.
2. Create the cookie
3. Do your normal test

No more popups.