How to use WeightedCucumberScenario class of net.serenitybdd.cucumber.suiteslicing package

I modified my project and added the feature files, following the Cucumber/Serenity conventions. All the scenarios with Scenario Outline are showing up in the report. Please create the project like : https://github.com/cliviu/serenity-cucumber5-starter.git. Please refer to the git issue:- https://github.com/serenity-bdd/serenity-core/issues/2190

I would normally not answer my own question , but I see few similar questions on SO.

For my case, removing fixed the issue.
testCompile ("io.cucumber:cucumber-spring:6.10.4")

However, to get the correct version of dependencies, if you are stuck in such issue, is to refer there github and check release notes and dependency tee.

For my case, the issue was on Cucumber-Serenity5.

So getting the dependecncies from build.gradle, worked. https://github.com/serenity-bdd/serenity-cucumber5/blob/master/build.gradle

Please note, the actual versions are defined in, gradle.proporties.
https://github.com/serenity-bdd/serenity-cucumber5/blob/master/gradle.properties

Take a look at Serenity BDD properties here.

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

I believe that this should be possible using the custom environments option when scheduling a run in Device Farm. Admittedly, I don't have experience with serenity but here is blog which uses cucumber tests.

https://aws.amazon.com/blogs/mobile/testing-mobile-apps-with-cucumber-and-appium-through-testng-on-aws-device-farm/

It looks like serenity is similar or extended from cucumber so in theory this might work.

[Edit]

Here are a few short gradle build tasks which should help to create a test package for Device Farm.

Note: this assumes that the dependencies are structured in the build.gradle file like this:

dependencies {

    testCompile(
            'net.serenity-bdd:serenity-junit:2.0.18',
            'net.serenity-bdd:serenity-cucumber:1.9.20',
            'org.assertj:assertj-core:3.11.1',
            'ch.qos.logback:logback-classic:1.2.3',
            'io.github.bonigarcia:webdrivermanager:3.0.0'
    )
}

sample build.gradle code

//source: https://stackoverflow.com/a/27455099/8016330
task getDeps(type: Copy) {
    from sourceSets.test.runtimeClasspath
    // if you need this from the dependencies in the build.gradle then it should be : 
    // from sourceSets.main.runtimeClasspath
    into 'build/libs/dependency-jars'
}

//packaging tests task which is generated from sample using gradle init
task packageTests(type: Jar) {
    dependsOn getDeps
    from sourceSets.test.output
    classifier = 'tests'
}

//create zip archive
//source: https://stackoverflow.com/a/36883221/8016330
task zip(type: Zip) {
    dependsOn packageTests
    from 'build/libs/'
    include '*'
    include '*/*' //to include contents of a folder present inside dependency-jars directory
    archiveName 'zip-with-dependencies.zip'
    destinationDir(file('build/libs/'))
}

Then you should be able to create the zip file using this command:

./gradlew clean zip

Note: You'll need the clean command otherwise it will package the previous zip archive in the new zip archive.

Hth

-James

Reading the extra comment / improves question, it sounds indeed like an Integration Test.

There are some need Integration Test libraries like JBehave, Serenity, Cucumber, etc which would probably better for setting this up.

With TestNG, you could create 3 tests, where each next test depends on the previous test. See code sample below, from testng dependency test

package com.mkyong.testng.examples.dependency;

import org.testng.annotations.Test;

public class App {

    @Test
    public void method1() {
        System.out.println("This is method 1");
    }

    @Test(dependsOnMethods = { "method1" })
    public void method2() {
        System.out.println("This is method 2");
    }

}

Here the most simple dependency is show. See the sample code for more complex cases, like groups etc. For setting up two test classes each with their own @Factory

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.

Scenario Outlines create a seperate scenario for each example element. You want a single scenario that looks for your tabs.

A better way to write this would be to name the tabs, e.g. foo-tabs and then write

Scenario: See foo tabs on main page
  When I am on the main page
  Then I should see foo tabs

And in your step definition do your programming to look for the tabs e.g.

Then "should see foo tabs" do
  foo_tabs.each do |tab|
    expect(page).to have # do something with the tab here
  end
end

(above is ruby'ish code, but you should be able to adapt to java)

Now you will have one scenario, and also if you add/remove a tab, you won't have to change your feature.

If I understand truly;

This should be your page class with @DefaultUrl annotation;

@DefaultUrl("https://google.com ")
public class GoogleHomePage extends PageObject {

   // Some Code 
}

After that you can call that like;

public class NavigateTo {

    GoogleHomePage googleHomePage;

    @Step("Open google homepage")
    public void googleHomePage() {

        googleHomePage.open();
    }
}

You can use a Utility class to feed the variables between classes.

For example, let's take an example of WebDriver driver initiation.

public class ClassUtility {

    public WebDriver baseDriver; 

}

You have a class where you want to access the webDriver.

public class InventoryPage extends ClassUtility {
private ClassUtility driver;
public InventoryPage(ClassUtility driver, ClassUtility fileElementLocator, ClassUtility elementLocatorProperties, ClassUtility page) {
    this.driver= driver;
    this.page =page;
}

@When("^Open the Google Page$")
public void openInventoryPage() throws Throwable {  
    driver.baseDriver = new FirefoxDriver();
    driver.baseDriver.get("www.google.com");
}

If you have to inject to different class, do it the similar fashion.

public class IntroductoryPage extends ClassUtility {

private ClassUtility driver;

public IntroductoryPage(ClassUtility driver, ClassUtility logger) {
    this.driver= driver;    
}

@When("^It should go to Account \"([^\"]*)\"")
public void openIntroductoryPage(String region) throws Throwable {
    driver.baseDriver.findElement(By.linkText("link")")).click();   
}

Please let me know if you need additional information. You can play around with the dependency injection as you wish.