How to use getCodePoint method of org.openqa.selenium.Enum Keys class

I ran across this same problem and could not find any solutions. Came up with a solution and posting it here, hope this helps someone with the same problem. I created a class to handle stale elements depending on their type, cssselector, id, etc and simply call it like I would any other page object.

public void StaleElementHandleByID (String elementID)
{
    int count = 0;
    boolean clicked = false;
    while (count < 4 && !clicked)
    {
        try 
        {
            WebElement yourSlipperyElement= driver.findElement(By.id(elementID));
            yourSlipperyElement.click(); 
            clicked = true;
        } 
        catch (StaleElementReferenceException e)
        {
            e.toString();
            System.out.println("Trying to recover from a stale element :" + e.getMessage());
            count = count+1;
        }
    }
}

I'd recommend only using this on elements you know cause problems for WebDriver.

Use the last modified to sort the directories and get the latest one

    File dir = new File("path");
    File[] files = dir.listFiles();
    File lastModified = Arrays.stream(files).filter(File::isDirectory).max(Comparator.comparing(File::lastModified)).orElse(null);
    System.out.println(lastModified);

using for loop

    File dir = new File("/path");
    File max = null;
    for (File file : dir.listFiles()) {
        if (file.isDirectory() && (max == null || max.lastModified() < file.lastModified())) {
            max = file;
        }
    }

sendkeys method is the problem as per the stack trace.

at org.openqa.selenium.remote.RemoteWebElement.sendKeys(RemoteWebElement.java:121)

Please try Actions class to first focus on the element then send required keys.

Actions actions = new Actions(driver);
actions.moveToElement(element);
actions.click();
actions.sendKeys("SOME DATA");
actions.build().perform();

It looks like those packages come from Selenium RC, from the times when it was created by ThoughtWorks.

See deprecated package list here, and migration guide here.

You probably want to migrate by disposing of the old dependency, re-writing the client code according to documentation, and use WebDriver.

In that case, your Maven groupID would be org.seleniumhq.selenium, as documented here.

You can also check pageloaded using following code

IWait<IWebDriver> wait = new OpenQA.Selenium.Support.UI.WebDriverWait(driver, TimeSpan.FromSeconds(30.00));

 wait.Until(driver1 => ((IJavaScriptExecutor)driver).ExecuteScript("return document.readyState").Equals("complete"));

 if (attribute.equals(null)) {
    return true;
  }`

If attribute is null then .equals call will lead to NPE. Try with attribute == null.

The behaviour is intended. Here is how it works -

1. You issue driver.get(B). It triggers the browser to open the webpage and then it doesnt have anything to do with the browser, so it doesnt care whether an alert is open or not.
2. When the page loads, pop-up dialog appears, but nothing happens on your code side or Eclipse.
3. When you try to perform another operation, it interacts with browser and sees an unexpected popup dialog.

Now, the problem occurs that modal dialog closes and still exception occurs, so try the following.

1. Enclose your second operation in a try/catch and handle UnhandledAlertException
2. Inside that catch block, perform, driver -> switch to -> alert -> accept
3. After the catch block, perform the second operation again.

I found the work around as below

1. Open terminal
2. Navigate to path where your chromedriver file is located
3. Execute any one of the below commands

Command1: xattr -d com.apple.quarantine <name-of-executable>

Example

/usr/local/Caskroom/chromedriver 
$ xattr -d com.apple.quarantine chromedriver 

(or)

Command2: spctl --add --label 'Approved' <name-of-executable>

Source: https://docwhat.org/upgrading-to-catalina

Note: This will work only with the file(s) where the above command is executed. If a new chromedriver is downloaded then the command has to be executed again on the newly downloaded file

Just for s&gs...

I timed each of the identifier methods finding the div above five separate times and averaged the time taken to find the element.

WebDriver driver = new FirefoxDriver();
driver.get("file://<Path>/div.html");
long starttime = System.currentTimeMillis();
//driver.findElement(By.className("class"));
//driver.findElement(By.cssSelector("html body div"));
//driver.findElement(By.id("id"));
//driver.findElement(By.name("name"));
//driver.findElement(By.tagName("div"));
//driver.findElement(By.xpath("/html/body/div"));
long stoptime = System.currentTimeMillis();
System.out.println(stoptime-starttime + " milliseconds");
driver.quit();

They are sorted below by average run time..

• CssSelector: (796ms + 430ms + 258ms + 408ms + 694ms) / 5 = ~517.2ms
• ClassName: (670ms + 453ms + 812ms + 415ms + 474ms) / 5 = ~564.8ms
• Name: (342ms + 901ms + 542ms + 847ms + 393ms) / 5 = ~605ms
• ID: (888ms + 700ms + 431ms + 550ms + 501ms) / 5 = ~614ms
• Xpath: (835ms + 770ms + 415ms + 491ms + 852ms) / 5 = ~672.6ms
• TagName: (998ms + 832ms + 1278ms + 227ms + 648ms) / 5 = ~796.6ms

After reading @JeffC 's answer I decided to compare By.cssSelector() with classname, tagname, and id as the search terms. Again, results are below..

WebDriver driver = new FirefoxDriver();
driver.get("file://<Path>/div.html");
long starttime = System.currentTimeMillis();
//driver.findElement(By.cssSelector(".class"));
//driver.findElement(By.className("class"));
//driver.findElement(By.cssSelector("#id"));
//driver.findElement(By.id("id"));
//driver.findElement(By.cssSelector("div"));
//driver.findElement(By.tagName("div"));
long stoptime = System.currentTimeMillis();
System.out.println(stoptime-starttime + " milliseconds");
driver.quit();

• By.cssSelector(".class"): (327ms + 165ms + 166ms + 282ms + 55ms) / 5 = ~199ms
• By.className("class"): (338ms + 801ms + 529ms + 804ms + 281ms) / 5 = ~550ms
• By.cssSelector("#id"): (58ms + 818ms + 261ms + 51ms + 72ms) / 5 = ~252ms
• By.id("id") - (820ms + 543ms + 112ms + 434ms + 738ms) / 5 = ~529ms
• By.cssSelector("div"): (594ms + 845ms + 455ms + 369ms + 173ms) / 5 = ~487ms
• By.tagName("div"): (825ms + 843ms + 715ms + 629ms + 1008ms) / 5 = ~804ms

From this, it seems like you should use css selectors for just about everything you can!