How to use scenarioResultIsUpToDate method of io.cucumber.core.plugin.ManualScenarioChecker class

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.

Check https://github.com/temyers/cucumber-jvm-parallel-plugin There is stated:

As of cucumber-jvm:4.0.0 parallel execution is supported natively by cucumber. As such, upgrading to Cucumber 4.0.0 is recommended and this plugin is no longer maintained.

So consider leave cucumber-jvm-parallel-plugin

It looks like you have in your pom.xml something like

<tags>"~@ignore"</tags>

try to change it to

    <tags>
      <tag>~@ignore</tag>
    </tags>

BTW proper new style is now not @ignore check https://github.com/cucumber/cucumber/tree/master/tag-expressions#migrating-from-old-style-tags

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/

Fortunately I am able to resolve this issue. With the latest Serenity version need to modify the page object class as below :

public class MobilePageObject extends PageObject {

    public MobilePageObject(final WebDriver driver) {
        super(driver, new Predicate<PageObject>() {
            @Override
            public boolean apply(PageObject page) {
                PageFactory.initElements(new AppiumFieldDecorator(((WebDriverFacade) page.getDriver()).getProxiedDriver()), page);

                return true;
            }
        });
    }
}

Also to get the proper Serenity reports use the command mvn verify command to execute the test.

Thanks for support!

You just need to add the endScenario method´s package to the glue in your CucumberOptions

@CucumberOptions(
    features = { ... },
    plugin = { ... },
    glue = {"...", "com.company.project.your.package"}
)

compile group: 'org.seleniumhq.selenium', name: 'selenium-chrome-driver', version: '3.0.1'

I'm not using Selenium. I'm using Gradle, Cucumber, Serenity.

The configuration tasks (deprecated, use target instead) comes from the plugin maven-antrun-plugin.

So it can't be used in the plugin maven-failsafe-plugin as in your first example.

Reading other pages, I found the solution:

In my POM, modify the Serenity dependencies below

<!--SERENITY DEPENDENCIES-->
        <dependency>
            <groupId>net.serenity-bdd</groupId>
            <artifactId>serenity-core</artifactId>
            <version>1.2.5-rc.6</version>
        </dependency>
        <dependency>
        <groupId>net.serenity-bdd</groupId>
        <artifactId>serenity-junit</artifactId>
        <version>1.2.5-rc.6</version>
        </dependency>
        <dependency>
            <groupId>net.serenity-bdd</groupId>
            <artifactId>serenity-cucumber</artifactId>
            <version>1.1.29</version>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>org.slf4j</groupId>
            <artifactId>slf4j-simple</artifactId>
            <version>1.7.25</version>
        </dependency>
        <!--SERENITY DEPENDENCIES-->

Add the next configuration to the POM

<properties>
    <cucumber.version>1.2.5</cucumber.version>
    <serenity.version>1.2.5-rc.6</serenity.version>
    <serenity.cucumber.version>1.1.29</serenity.cucumber.version>
       <java.version>8</java.version>
   </properties>

And use this plugin:

<plugin>
                 <groupId>net.serenity-bdd.maven.plugins</groupId>
                 <artifactId>serenity-maven-plugin</artifactId>
                 <version>1.1.29</version>
                 <executions>
                     <execution>
                         <id>serenity-reports</id>
                         <phase>post-integration-test</phase>
                         <goals>
                             <goal>aggregate</goal>
                         </goals>
                     </execution>
                 </executions>
             </plugin>

After running my SerenityRunner, the system runs the feature classes without problem. This is the result of that:

[main] INFO net.serenitybdd.core.Serenity - 

        __    _____ _____ ____ _____   ____   _    ____  ____  _____ ____  
  _     \ \  |_   _| ____/ ___|_   _| |  _ \ / \  / ___|/ ___|| ____|  _ \ 
 (_)_____| |   | | |  _| \___ \ | |   | |_) / _ \ \___ \\___ \|  _| | | | |
  _|_____| |   | | | |___ ___) || |   |  __/ ___ \ ___) |___) | |___| |_| |
 (_)     | |   |_| |_____|____/ |_|   |_| /_/   \_\____/|____/|_____|____/ 
        /_/          

Thanks for the help Grasshopper!!!

This is a question related to upgrading to Cucumber 6, which has a different API, syntax and and architecture compared to Cucumber 2. You will need to rewrite many of the step definition methods, as the regular expressions used in Cucumber 2 will need updating, and the parameter conversion logic will also need updating (different classes are used).