How to use Enum InternetExplorerDriverLogLevel class of org.openqa.selenium.ie package

I would argue storing the files in the page class itself. Loading from properties file would incur additional overhead or parsing a large file. Maintaining such a file would also be harder, even with a good tool support you would be forced to use CTRL + F more than you should.

Even on a more conceptual level it feels wrong. A good fit for storing in properties files are configurable parameters, and especially the ones that are good candidates to be tweaked in runtime.

Locators don't have this nature. If the benefit you're seeking is declaring in a central place you should instead use dedicated constant class, which will give you much better refactoring options.

I can show you how to get the description partially using reflection.

First of all, we have to fix the Annotation @Name because you didn't add RetentionPolicy:

@Target({ElementType.FIELD, ElementType.TYPE, ElementType.CONSTRUCTOR})
@Retention(value = RetentionPolicy.RUNTIME)
public @interface Name {
    String Description() default "";
}

Now, what I did and tested, we create storage for the names and we're gonna store them when initializing the Page Objects like this:

public class NameStore {
    public static HashMap<WebElement, String> map = new HashMap<>();

    public static void store(Object pageObject) {
        Field[] fields = pageObject.getClass().getDeclaredFields();
        for (Field field : fields) {
            Name annotation = field.getAnnotation(Name.class);
            if (annotation != null) {
                try {
                    map.put((WebElement) field.get(pageObject), annotation.Description());
                } catch (IllegalAccessException e) {
                    e.printStackTrace();
                }
            }
        }
    }

    public static String getDescription(WebElement element) {
        return map.get(element);
    }
}

You pass a Page Object as an argument, @Name annotation is read and stored into the HashMap<WebElement, String>

Initialize name storing in a constructor:

    public PageObject(WebDriver driver) {
        PageFactory.initElements(driver, this);
        NameStore.store(this); //THIS IS CRUCIAL. Also make sure that's always AFTER PageFactory initialization
    }

And now, to update your click method:

public static void click(WebElement element) throws Throwable {
        try {
            element.click();
        } catch(ElementNotInteractableException E1) {
            throw new UnableToInteractWithElementException("Unable To Interact With " + NameStore.get(element));
        }
    }

Hope it helps!

Disclaimer: I didn't test it in the context of multi-threading. I did not test in the context of a constructor.

Please read this Martin Follower's article - Page Object.

A quotation:

Despite the term "page" object, these objects shouldn't usually be built for each page, but rather for the significant elements on a page

Imagine a page which has over of dozen tabs, panels etc, and each one have a few fields, buttons etc. It would be impractical to create a huge class for such a page, it would certainly have 300-500 or more lines of code. Such a class would be very hard to maintain.

It's better (in my opinion) to create several small classes (page objects), each for a specific section of the page, each one containing only a few elements, each no more than 50-100 lines of code. We call these classes page fragments instead of page objects, but the concept is the same.

But it will vary from person to person and everyone may have a different opinion on this topic.

for (String handle : driver.getWindowHandles()) {
    driver.switchTo().window(handle);
    System.out.println(String.format("handle: %s, url: %s", handle, driver.getWebDriver().getCurrentUrl()));
} 

I was looking for something similar just recently and found that the Changelog is probably the best place to look at for compatibility questions:

https://github.com/SeleniumHQ/selenium/blob/master/java/CHANGELOG

(used to be at when Selenium was hosted on Google Code).

All the most recent version have a support up to Firefox v XX comment at the very top of each version. The older ones you have to read in the comments a little, but they will say which version is the greatest supported for that release.

Hope this helps.

Try this:

WebElement element = driver.findElement(By.id("id value"));  
String val = element.getAttribute("innerText")

You sure can. Here's some pseudo-code.

assertTrue(
    driver.findElement(
        By.cssSelector("div#parent > div:nth-child(1) > textarea#field3")
    ).isDisplayed()
);

The logic here pretty much says:

Look for the first div that is under <div id="parent">, that is immediately followed by <textarea id="field3">. If this assertion fails, that means it's out of order, and the third field is NOT first.

(note, that div#parent is obviously subject to change. You need to change it to the parent of these divs, and you may also need to fiddle about with the :nth-child(n) depending on the order)

Just specify the path to the binary of the version..may be, like-

FirefoxBinary binary = new FirefoxBinary(new File("path_to_bin"));
FirefoxProfile profile = new FirefoxProfile();
WebDriver driver = new FirefoxDriver(binary, profile);

You can set the useAutomationExtension capability to false.

    ChromeOptions options = new ChromeOptions();
    options.setExperimentalOption("useAutomationExtension", false);
    WebDriver driver = new ChromeDriver(options);

This capability will help to not load Chrome Automation extension. Due to which, "Failed to load extension" popup would not appear.

But please note you will not be able to perform any window resizing/positioning operations without the Chrome automation extension.

Hope this helps!

Source : https://bugs.chromium.org/p/chromedriver/issues/detail?id=1749