How to use rotation method of org.openqa.selenium.Interface Rotatable class

Take a look at the section about filling in forms using webdriver in the selenium documentation and the javadoc for the Select class.

To select an option based on the label:

Select select = new Select(driver.findElement(By.xpath("//path_to_drop_down")));
select.deselectAll();
select.selectByVisibleText("Value1");

To get the first selected value:

WebElement option = select.getFirstSelectedOption()

Looks like timing issue to me. After you redirect to checkout, you might want to wait for the elements before interacting. See Explicit Waits in documentation.

WebDriverWait wait = new WebDriverWait(driver, 60);// 1 minute 
wait.until(ExpectedConditions.visibilityOfElementLocated(By.id("order_billing_name")));
driver.findElement(By.id("order_billing_name")).sendKeys(a.getName());

As I told the question is in implementation of JUnit.

You can see that:

Parallelized extends Parametrized extends Suite extends ParentRunner

on the other hand:

ConcurrentTestRunner extends BlockJUnit4ClassRunner extends ParentRunner

hence they are from different hierarchies of inheritance.

And now what you have to look at is implementation of the:

org.junit.runners.ParentRunner#getChildren

method. For the org.junit.runners.BlockJUnit4ClassRunner it is:

protected List<FrameworkMethod> computeTestMethods() {
    return getTestClass().getAnnotatedMethods(Test.class);
}

which generates all methods with annotations. But for org.junit.runners.Parameterized it is:

for (int i= 0; i < parametersList.size(); i++)
  runners.add(newtestClassRunnerForParameters(getTestClass().getJavaClass(),
                parametersList, i));

And the last one gives only classes.

Proposal: override your Parallelized class with definition of org.junit.runners.ParentRunner#getChildren from BlockJUnit4ClassRunner.

This is what I have been doing and it has worked so far for me.

ChromeOptions chromeOptions = new ChromeOptions();
chromeOptions.addArgument("--log-level=3");
chromeOptions.addArgument("--silent");
WebDriver driver = new ChromeDriver(chromeOptions);

This should select the element you want

./ancestor::div[contains(concat(' ', @class, ' '), ' x-grid-view ')][1]

In plain English: Of all the ancestor div elements that have ' x-grid-view ' in their class, select the first (closest) one.

Notes:

• I concat spaces as a defensive measure to prevent partial matches.
• current() is an XSLT function, not an XPath one. It has no meaning outside of XSLT. The current node is expressed as . in XPath.

Best practice, according to most sites I've seen, is to keep the asserts out of the page objects. One example is below from the Selenium docs.

http://www.seleniumhq.org/docs/06_test_design_considerations.jsp#page-object-design-pattern

There is a lot of flexibility in how the page objects may be designed, but there are a few basic rules for getting the desired maintainability of your test code.

Page objects themselves should never make verifications or assertions. This is part of your test and should always be within the test’s code, never in an page object. The page object will contain the representation of the page, and the services the page provides via methods but no code related to what is being tested should be within the page object.

There is one, single, verification which can, and should, be within the page object and that is to verify that the page, and possibly critical elements on the page, were loaded correctly. This verification should be done while instantiating the page object. In the examples above, both the SignInPage and HomePage constructors check that the expected page is available and ready for requests from the test.

The page object should return things like product name, product price, currently selected quantity, and so on. The test code would then assert that the returned string matches what is expected.

assert_message() would become getMessage() and return the message as a String. See below.

public String getMessage()
{
    return driver.findElement(messageLocator).getText();
}

(NOTE: read on for why I've changed the PageFactory element to a locator here.)

and then in your test code, you would have

Assert.assertEquals(editPost.getMessage(), "Post published. View post");

Now you've kept the assert code in your test script and out of the page object.

Looking at your code, I would make some further recommendations.

1. I would suggest you read up on some Java naming conventions. There are a number of sites that have recommendations and I think there are a lot of similarities between them but here's the oracle recommendations to start with. Your method names should be

   verbs, in mixed case with the first letter lowercase, with the first letter of each internal word capitalized.

   So assert_message() would turn into assertMessage() and so on. The _s make it look more like python.

2. Order of preference for locators: ID, CSS selector, and in rare circumstances, XPath. ID should always be your first choice because it (by W3C definition) should be unique on the page. CSS selector should be next because it's the fastest (in my testing faster than ID), has the best browser support, and is most consistently implemented across browsers. XPath should be reserved only for things that cannot be done by CSS seletors like finding an element by contained text. XPath locators are poor performers compared to CSS selectors and do not have the same level of support as CSS selectors. For example, your XPath locator can easily be converted to a CSS selector, "#message > p".

   Here are some CSS selector references to get you started.

   CSS Selectors reference

   CSS Selector tips

3. Drop PageFactory. Yes, it seems to make things easier but I think in many situations it causes more problems, like stale element exceptions and the like. Prefer instead to scrape the page as needed. Declare all locators at the top of the class and use them in methods when needed.

   public class EditPost {
   
       WebDriver driver;
   
       By messageLocator = By.cssSelector("#message > p")
   
       public EditPost(WebDriver editPostDriver)
       {
           this.driver = editPostDriver;
       }
   
       public String getMessage()
       {
           return driver.findElement(messageLocator).getText();
       }
   }
   

I know this is more than you asked but hopefully it's helpful.

For Chromedriver try out with:

String downloadFilepath = "/path/to/download";
HashMap<String, Object> chromePrefs = new HashMap<String, Object>();
chromePrefs.put("profile.default_content_settings.popups", 0);
chromePrefs.put("download.default_directory", downloadFilepath);
ChromeOptions options = new ChromeOptions();
options.setExperimentalOption("prefs", chromePrefs);
DesiredCapabilities cap = DesiredCapabilities.chrome();
cap.setCapability(CapabilityType.ACCEPT_SSL_CERTS, true);
cap.setCapability(ChromeOptions.CAPABILITY, options);
WebDriver driver = new ChromeDriver(cap);

Note:- Use File.separator to handle slashes, it will put syntax as per os it is executing the code. In windows you need to use \\ for path while if you are using linux or mac then use //

Hope this helps. :)

You don't have your XPath syntax right. You need quotes round the text attribute values you're matching against. Try:

d.findElement(By.xpath("//select[@id='category']/option[@id='cat2']")).click();

Don't use sleep!!!

public static WebElement findElement(WebDriver driver, By selector, long timeOutInSeconds) {
    WebDriverWait wait = new WebDriverWait(driver, timeOutInSeconds);
    wait.until(ExpectedConditions.presenceOfElementLocated(selector));

    return findElement(driver, selector);
}