How to use getName method of org.openqa.selenium.grid.distributor.httpd.DistributorServer class

You should use file address like this:

driver.get("C:\\Users\\sharmayo\\Desktop\\testlogin.html");

instead of:

driver.get("C://Users//sharmayo//Desktop//testlogin.html");

I normally send an empty key to the element so it gets focused. So for example:

element.send_keys ""

The key thing here is the resolution, you must ensure that resolution is the same for base "golden" images and those you capture during test.

1. Set size of the browser window to fixed size, eg. (1920x1080),
2. Make all screenshots in this resolution,
3. During the test: before each image-comparison check if the window size is (1920x1080) if not I change it temporarily,
4. Take screenshot,
5. Compare image with original "golden" img
6. Do window maximize

Other solution is to capture screenshots of single WebElement rather than whole page, because WebElements often are resolution independent.

Create a new implementation of FieldDecorator.

When you use the PageFactory you are probably calling

 public static void initElements(ElementLocatorFactory factory, Object page)

This would become

 public static void initElements(FieldDecorator decorator, Object page)

Your FieldDecorator could behave similarly to the DefaultFieldDecorator except wrap the proxy in your custom type.

See the classes here [source]

Okay, the script obviously kicks in when the clear() method clears the input and leaves it empty. The solutions it came up with are given below.

1. The naïve one, presses Backspace 10 times:

   String b = Keys.BACK_SPACE.toString();
   searchField.sendKeys(b+b+b+b+b+b+b+b+b+b + username);
   

   (StringUtils.repeat() from Apache Commons Lang or Google Guava's Strings.repeat() may come in handy)

2. The nicer one using Ctrl+A, Delete:

   String del = Keys.chord(Keys.CONTROL, "a") + Keys.DELETE; 
   searchField.sendKeys(del + username);
   

3. Deleting the content of the input via JavaScript:

   JavascriptExecutor js = (JavascriptExecutor)driver;
   js.executeScript("arguments[0].value = '';", searchField);
   searchField.sendKeys(username);
   

4. Setting the value of the input via JavaScript altogether:

   JavascriptExecutor js = (JavascriptExecutor)driver;
   js.executeScript("arguments[0].value = '" + username + "';", searchField);
   

Note that javascript might not always work, as shown here: Why can't I clear an input field with javascript?

I just wrote a quick function for you. hope it helps!

/**
 * Get all <code><option/></code> innerHTML attributes
 *
 */
List<String> getAllOptions(By by) {
    List<String> options = new ArrayList<String>();
    for (WebElement option : new Select(driver.findElement(by)).getOptions()) {
        String txt = option.getText();
        if (option.getAttribute("value") != "") options.add(option.getText());
    }
    return options;
}

Now executing:

getAllOptions(By.id("vehicleTypeName"));

will return:

["Hatchback Cars", "Sedan Cars"...] // of course in List<> representation..

I've run into the same issue.

Apparently Chrome automatically updates itself. Yesterday (Oct 29 '19) My ChromeDriver started complaining that it was not compatible with Chrome 78. I updated the driver to the 78 version. I started to get random org.openqa.selenium.NoSuchElementException exceptions when trying to find elements that I confirmed were there. The findElement[s] also work when I used breakpoints. I also tried implicit waits, with only limited success.

I tried zsbappa's ChromeOption solution but no joy.

Google makes it hard to get old versions of Chrome, but I found version 76 at https://www.neowin.net/news/google-chrome-76-offline-installer/. Beware, the online installer installs the latest version. I reverted to the driver for 76 and all is good. All my Selenium tests are working again.

My conclusion is that the Chrome 78 and it's associated driver has a race condition where Selenium attempts to interrogate the web page before it's complete.

If you have the DOM parsed already into JSoup, then I would recommend using JSoup. It is much faster than selenium, since it does not need to bother with a "living" DOM. Selenium must always check if the element handles are still valid before doing any operations with them.

If you can, avoid selenium altogether, since its overhead is really noticeable when you do serious scraping. Selenium shines, however, if your content is dynamically generated by JavaScript in the client. JSoup can't handle this at all, since it does not execute JavaScript.

Addendum to answer a comment

Short answer : It depends!

Longer: If the website you are scraping is generated by JavaScript and it does not change after generation, it is perfectly fine to access it with selenium, especially, if the DOM is complex and would take long to read into JSoup, although JSoup is fairly fast. However, JSoup will generate the DOM in memory again, so if your DOM is huge you will not only have it in a memory consuming way in selenium, but also in JSoup. This may or may not be an issue in your case, but it is worth keeping in mind.

From my personal experience I would kill the selenium process as soon as possible after getting the final HTML and parse this in JSoup again, since it is as you say: Jsoup scraping is way easier than the corresponding selenium selector constructs, especially if you are sure that any changes in the DOM after the initial creation are irrelevant to your scraping.

To work with Selenium 3.4.0 & Mozilla Firefox 53.x you need to download the latest geckodriver v0.16.1 from here. Save it in your machine & provide absolute path of the geckodriver in your code.

Ensure that you have updated the pom.xml with the required dependency as follows:

<dependency>
        <groupId>org.seleniumhq.selenium</groupId>
        <artifactId>selenium-java</artifactId>
        <version>3.4.0</version>
</dependency> 

It is recommended to use the WebDriver interface rather than to use the FirefoxDriver implementation.

Your code will look like:

System.setProperty("webdriver.gecko.driver", "C:\\Utility\\BrowserDrivers\\geckodriver.exe");
WebDriver driver = new FirefoxDriver();       
driver.navigate().to("http://www.google.com");

Provide the following commands to flush out the previous dependencies, install the new dependencies & execute your test:

>mvn clean
>mvn install
>mvn test