How to use MethodInvoker class of net.thucydides.junit.internals package

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

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

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.

maven-failsafe-plugin has no notion of "packages". The notion of "suites" is related to junit4 Suite.

To solve my problem above, I did the following:

In each "features.area" I created a "TestSuiteStub":

import org.junit.runner.RunWith;
import org.junit.runners.Suite;

/**
 * This will be processed by groovy-maven-plugin.
 */
@RunWith(Suite.class)
@Suite.SuiteClasses({
/* add test Stories after this ANCHOR */
})
public class TestSuiteStub {
    /* Suite holder */
}

I then used the groovy-maven-plugin with execute goal and the following script:

// find all TestSuiteStub.java
new File("${project.build.testSourceDirectory}/features").  // exploits the "complication" in Maven interpolation and GStrings
  traverse(type: groovy.io.FileType.FILES, nameFilter: ~/TestSuiteStub\.java/) { stub ->
    println 'Using: ' + stub

    // in the same dir as TestSuiteStub.java, find all *Story.java
    def stories = new StringBuilder()
    new File(stub.parent).
      eachFileMatch(groovy.io.FileType.FILES, ~/.*Story\.java/) { story ->
        stories.append story.name.replace('java', 'class')
        stories.append ', ' // will leave a comma at end of list, but javac seems to be ok with that
      }
    println 'Found: ' + stories

    // write out TestSuite.java
    def suite = new File(stub.parent + '/TestSuite.java')
    suite.delete()
    println 'Writing: ' + suite
    stub.eachLine() { line ->

      if(line.contains('Stub'))
        suite.append line.replace('TestSuiteStub', 'TestSuite') + System.getProperty('line.separator')
      else
        suite.append line + System.getProperty('line.separator')

      if(line.contains('ANCHOR'))
        suite.append stories + System.getProperty('line.separator')
    }
  }

This will process each of the TestSuiteStub and generate a TestSuite. So after running this (you can use mvn test-compile to run this, without running your tests), I have something like:

src/test/java
+-features.areaA
| +-SomeStory.java
| +-AnotherStory.java
| ...
| +-TestSuiteStub.java
| +-TestSuite.java
+-features.areaB
| +-DifferentStory.java
| +-OtherStory.java
| ...
| +-TestSuiteStub.java
| +-TestSuite.java
...

where the first TestSuite will look something like:

import org.junit.runner.RunWith;
import org.junit.runners.Suite;

/**
 * This class will be processed by groovy-maven-plugin.
 */
@RunWith(Suite.class)
@Suite.SuiteClasses({
/* add test Stories after this ANCHOR */
SomeStory.class, AnotherStory.class,
})
public class TestSuite {
    /* Suite holder */
}

To make maven-failsafe-plugin pick this up, I configured it like this:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-failsafe-plugin</artifactId>
  <version>${failsafe.plugin.version}</version>
  <configuration>
    <includes>
      <include>features.*.*Suite</include>
    </includes>
    <parallel>suites</parallel>
    <threadCountSuites>4</threadCountSuites>
  </configuration>
  <executions>
    <execution>
      <goals>
        <goal>integration-test</goal>
        <goal>verify</goal>
      </goals>
    </execution>
  </executions>
</plugin>

Lastly I also added *Suite.java to my .gitignore.

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.

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

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.

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/