How to use Interface NeedsLocalLogs class of org.openqa.selenium.logging package

Use findElement instead of findElements

driver.findElement(By.xpath("//input[@id='invoice_supplier_id'])).sendKeys("your value");

OR

driver.findElement(By.id("invoice_supplier_id")).sendKeys("value", "your value");

OR using JavascriptExecutor

WebElement element = driver.findElement(By.xpath("enter the xpath here")); // you can use any locator
 JavascriptExecutor jse = (JavascriptExecutor)driver;
 jse.executeScript("arguments[0].value='enter the value here';", element);

OR

(JavascriptExecutor) driver.executeScript("document.evaluate(xpathExpresion, document, null, 9, null).singleNodeValue.innerHTML="+ DesiredText);

OR (in javascript)

driver.findElement(By.xpath("//input[@id='invoice_supplier_id'])).setAttribute("value", "your value")

Hope it will help you :)

Implicit and Explicit Waits

Implicit Wait

An implicit wait is to tell WebDriver to poll the DOM for a certain amount of time when trying to find an element or elements if they are not immediately available. The default setting is 0. Once set, the implicit wait is set for the life of the WebDriver object instance.

driver.manage().timeouts().implicitlyWait(10, TimeUnit.SECONDS);

Explicit Wait + Expected Conditions

An explicit waits is code you define to wait for a certain condition to occur before proceeding further in the code. The worst case of this is Thread.sleep(), which sets the condition to an exact time period to wait. There are some convenience methods provided that help you write code that will wait only as long as required. WebDriverWait in combination with ExpectedCondition is one way this can be accomplished.

WebDriverWait wait = new WebDriverWait(driver, 10);
WebElement element = wait.until(
        ExpectedConditions.visibilityOfElementLocated(By.id("someid")));

However, I am unsure how the method determines equality?

The driver generates a reference for each encountered HTMLElement object in the document and always returns the same reference for an HTMLElement object.

This reference is stored in the WebElement.id property on the client side and has nothing to do with the id attribute used with a locator.

So to determine the equality between two WebElement, the client simply tests the reference stored in WebElement.id.

And are there any circumstances where the two web elements are in fact the same but the method shows they are different?

Technically speaking, no it never happens and it would be a serious issue if it was the case.

But it kind of depends on what you mean by the same. For instance a button can look the same at two different moments, but may have been replaced by an identical one which would generate a new reference. This is the case when the page or some parts are reloaded:

  driver.get("http://stackoverflow.com/");

  WebElement elementA = driver.findElement(By.cssSelector("#logo"));
  WebElement elementB = driver.findElement(By.cssSelector("#logo"));

  boolean same1 = elementA.equals(elementB);  // return true

  elementB.click();  // reloads the page, all the previous web element are now obsolete

  WebElement elementC = driver.findElement(By.cssSelector("#logo"));

  boolean same2 = elementA.Equals(elementC);  // return false

Unfortunately, WebDriver can't handle these (or any other browser or OS dialog). Moreover, they tend to look differently across browsers / systems / language settings, so there's probably no definite answer. You'll need to detect and handle every possible case in order to make it work everywhere. Your options include:

• The Robot class, it allows you to "press" programatically anything on the keyboard (or clicking blindly) and therefore getting rid of the dialog by, say, pressing Enter or Esc. However, as told above, any advanced interaction is dependant on OS / language / printer.

  // press Escape programatically - the print dialog must have focus, obviously
  Robot r = new Robot();
  r.keyPress(KeyEvent.VK_ESCAPE);
  r.keyRelease(KeyEvent.VK_ESCAPE);
  

• AutoIt. It's a Windows program useful for handling any system-level automation. Same dependancy as above.

That's more or less it. If you can avoid the print dialog, try to take screenshot of the page and print it using standard Java tools.

You can use the findElements method to find all the matched element and then iterate the loop for only the matched element. findElements method will find all the matched elements based on the locator.

Please check the modified code

//It will match all the product name based on the xpath (index alone needs to be removed from your index)
      List<WebElement> element = driver.findElements(By.xpath("(//td[@data-id='product_name'])"));

        int size=element.size();

        for(int i=0;i<size;i++){
            productsInOrder.add(element.get(i).getText()); 
        }

Found simple solutin for JAVA Seleniun Google Chrome

    System.setProperty("webdriver.chrome.driver", "chromedriver.exe");
    ChromeOptions options = new ChromeOptions();
    options.addArguments("headless");
    return new ChromeDriver(options);

ElementNotInteractableException

ElementNotInteractableException is the W3C exception which is thrown to indicate that although an element is present on the HTML DOM, it is not in a state that can be interacted with.

Reasons & Solutions :

The reason for ElementNotInteractableException to occur can be numerous.

1. Temporary Overlay of other WebElement over the WebElement of our interest :

   In this case, the direct solution would have been to induce ExplicitWait i.e. WebDriverWait in combination with ExpectedCondition as invisibilityOfElementLocated as folllows:

   WebDriverWait wait2 = new WebDriverWait(driver, 10);
   wait2.until(ExpectedConditions.invisibilityOfElementLocated(By.xpath("xpath_of_element_to_be_invisible")));
   driver.findElement(By.xpath("xpath_element_to_be_clicked")).click();
   

   A better solution will be to get a bit more granular and instead of using ExpectedCondition as invisibilityOfElementLocated we can use ExpectedCondition as elementToBeClickable as follows:

   WebDriverWait wait1 = new WebDriverWait(driver, 10);
   WebElement element1 = wait1.until(ExpectedConditions.elementToBeClickable(By.xpath("xpath_of_element_to_be_clicked")));
   element1.click();
   

2. Permanent Overlay of other WebElement over the WebElement of our interest :

   If the overlay is a permanent one in this case we have to cast the WebDriver instance as JavascriptExecutor and perform the click operation as follows:

   WebElement ele = driver.findElement(By.xpath("element_xpath"));
   JavascriptExecutor executor = (JavascriptExecutor)driver;
   executor.executeScript("arguments[0].click();", ele);
   

In my case, the chrome browser version and chromedriver versions were incompatible. Chrome updated automatically from 56 to 57 and my chromedriver version was 2.27. The 2 issues throwing 'org.openqa.selenium.WebDriverException: unknown error: cannot get automation extension' error (when maximizing the browser and when taking screenshots), where fixed after updating to cromdriver version 2.28.

Yes, that's the default behavior of TestNG and I had introduced it through that pull request to fix the bug https://github.com/cbeust/testng/issues/2022

To set the JVM arguments in intelliJ, choose Run > Edit Configurations, and add this JVM argument in the VM options section after -ea (which would be there by default.

For more information on editing configurations, please refer to the official documentation here

Added screenshot for easy to find in Intellij

Argument value

-ea -Dtestng.dtd.http=true

If the above does not work do at template level, this will fix it, which is

Run--> Edit configuration --> template --> testng