How to use LineFilters class of io.cucumber.core.plugin package

I was also facing issues in initiating safari browser on mac machine, and below solution helped me

if (browserType.equals("safari")) {
            // System.setProperty("webdriver.safari.driver", workingDir +
            // "//driver//SafariDriverServer.exe");
            System.setProperty("webdriver.safari.driver",
                    "/driver/SafariDriver.safariextz");
            System.setProperty("webdriver.safari.noinstall", "true");
            DesiredCapabilities desiredCapabilities = DesiredCapabilities
                    .safari();
            SafariOptions safariOptions = new SafariOptions();
            safariOptions.setUseCleanSession(true);
            safariOptions.getUseCleanSession();
            safariOptions.setUseCleanSession(true);
            desiredCapabilities.setCapability(SafariOptions.CAPABILITY,
                    safariOptions);

            // deleteCookies();
            driver = new EventFiringWebDriver(new SafariDriver());

            ThreadDriver.set(driver);
            // driver.manage().window().setSize(new Dimension(1024, 850));
            getDriver().manage().timeouts().implicitlyWait(3,
                    TimeUnit.SECONDS);
            wait = new WebDriverWait(driver, 30);
        }

İ have solved the issue through making the constructor in the step definition file empty, defining the driver variable as static in the hook definition file and instantiating as a class object in the step definition file where İ called the getDriver method.

İt seems that serenity needs an empty constructor in the step definition file.

Below are the steps from John Ferguson Smart' blog, author of Serenity-BDD (considering that you have installed Cucumber for Java plugin).

Running Cucumber with Serenity feature files directly from IntelliJ:

IntelliJ provides excellent integrated support for Cucumber feature files. You can even run features simply by right-clicking on the feature file. But this won’t work when you are using Cucumber with Serenity, as Serenity needs to instrument the feature file before execution. Fortunately, this is easy to fix. Here’s how:

• Click on the feature file you want to run
• In the Run menu Select Run…
• In the contextual menu, select the feature, then “Edit…”
• You should now see the ‘Edit Configuration Settings’ window. Set the main class to ‘net.serenitybdd.cucumber.cli.Main’
• Change the Glue field to the root package of your project (or of your step definitions)
• Click Apply

Now you can run your feature directly by right-clicking on the feature file.

P.S. Not all versions of Cucumber for Java plugin works correctly, especially when you have just updated IntelliJ IDEA to the latest version. I can confirm that next setup works correctly:

• IntelliJ IDEA 2018.2.3 (Community version);
• Cucumber for Java plugion version 182.3934;
• net.serenity-bdd:serenity-core:2.0.6;
• net.serenity-bdd:serenity-cucumber:1.9.18

Eventually I discovered that I had first to setup the Failsafe plugin, and then make it communicate with the CucumberMain class. Then, from the CLI, executing either mvn verify or mvn test with the list of tests that I want to execute made the trick

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!!!

If you are trying to run an After hook after each scenario tagged with "@tag1" in your example, you should mark the After hook with "@tag1". For more information on tagged hooks, please refer to the Cucumber documentation.

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

Take a look at Serenity BDD properties here.

There are serenity.verbose.steps and serenity.logging properties which you might find useful.

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).