How to use fromTheConfiguredPaths method of net.serenitybdd.cucumber.model.StoredFeatureFile class

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);
        }

After trying a number of different ways, I used reflection within the class to pull all fields, and then used .isPresent(); to check if the element is on the page. This solution requires this method to be placed in each class that you want to test, which I was trying to avoid.

Solution:

SuiteRunner

@RunWith(CucumberWithSerenity.class)
@CucumberOptions(features = "src/test/resources/features/checkElems")
public class RegressionTestSuite {}

Feature File: CanFindElems.feature

Feature: Check if WebPage Object elements can be found

  Scenario: Check if the page's elements are reachable
    Given navigate to webpage
    Then check page elements

Test Class

public class CanFindElemsTest {

  // Change the class
  ClassYouAreTesting page;

  @Given("^navigate to webpage$")
  public void navigate_to_webpage() throws Exception {

    page.open();
  }


  @Then("^check page elements$")
  public void check_page_elements() throws Exception {

    page.checkPageElementsExist();
  }
}

Page Class

public class SomeWebPage extends PageObject {

  @FindBy(id = "someID")
  private WebElementFacade someElement;

  @FindBy(linkText = "some text")
  private WebElementFacade someLink;

  @FindBy(className = "some-class")
  private WebElementFacade anotherElement;


  public void checkPageElementsExist() throws Exception {

    Field[] allFields = getClass().getDeclaredFields();
    for (Field field : allFields) {

      if (field.get(this) instanceof WebElementFacade) {

        WebElementFacade f = (WebElementFacade) field.get(this);

        if (!f.isPresent()) {

          System.out.println("ElementNotFound: " + field.getName());
        } else {

          System.out.println("Found: " + field.getName());
        }
      }
    }
  }

}

I think this is a Chromedriver bug, as indicated by the stack trace.

1) Ignored tests are marked as suspended and runs but with mocked web driver usage. I had to add StepEventBus.getEventBus().currentTestIsSuspended() check before my REST requests.

2) @Ignored annotation works unexpected for me. I've added @Unimplemented annotation and process it in defifnitions before hook.

@Before
public void setTheStage(final Scenario scenario) {
    final StepEventBus eventBus = StepEventBus.getEventBus();
    if (scenario.getSourceTagNames().contains("@Unimplemented") && !eventBus.currentTestIsSuspended()) {
        eventBus.suspendTest(TestResult.IGNORED);
    }

You can use tagging for that purpose. Information about that feature can be found in Serenity BDD official documentation.

Just a short excerpt, tags are added to jUnit tests using WithTag annotation. The following will add a tag of type feature (this is a default Serenity type) with name Reporting:

@WithTag(type="feature", name="Reporting")

Then you can run tests with this tag with jUnit like this:

mvn clean verify -Dtags="feature:Reporting"

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.

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.

PageObject has a getDriver() method, which you should use if you require the use of WebDriver.

I strongly suggest you study the Serenity BDD's Manual if you are going to work with the framework. You should find an answer to most questions there. Alternatively, check Serenity BDD Users Group.

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