How to use version method of org.openqa.selenium.docker.v1_41.V141Docker class

You should use WebDriverWait with some expected condition. For example,

WebDriverWait wait = new WebDriverWait(driver, 5); // sets timeout to 5 seconds
wait.until(...); // Use ExpectedCondition to set the condition you need to check for (i.e. element to be clickable, frame to be visible, etc.)
// Do your thing.

The until method will return an object type relative to the function passed. For example, until(ExpectedConditions.elementToBeClickable(...)); will return a WebElement object you can use to exert an action on (like clicking on it).

Lastly, you should wrap those lines in a try/catch and handle the TimeoutException the wait method will throw if the condition never arises.

To summarize, structurally, your code should look something like this:

// instantiate the WebDriver
...
int timeoutMax = 2; // The maximum number of seconds you wish to wait before timing out (let's assume 2 seconds is reasonable for your case)
try {
    By checkboxLocator = By.id("checkboxID"); // Locate element by some criteria (id, css, xpath). Using by ID for illustration purposes only
    By buttonLocator = By.id("buttonID"); // same as above
    By popupLocator = By.id("frameid"); // same as above
    WebDriverWait wait = new WebDriverWait(driver, timeoutMax);
    wait.until(ExpectedConditions.frameToBeAvailableAndSwitchToIt(popupLocator)); // assuming it is an iframe

    // The next lines will not be executed if the "Don't display this again" and clicking "OK" were clicked before (locating the frame will timeout because it not be visible)
    WebElement checkbox = wait.until(ExpectedConditions.elementToBeClickable(checkboxLocator));
    WebElement okBtn = wait.until(ExpectedConditions.elementToBeClickable(checkboxLocator));
    checkbox.click();
    okBtn.click();
    driver.switchTo().defaultContent(); // Switch back to default window
} catch (TimeoutException exc) {
    // Handle exception (i.e. log a warning) - This should be thrown as long as the modal dialog doesn't become visible
    // If modal dialog ever becomes visible again, clicking on the checkbox and OK button will be executed again.
}

Something like this should work. Of course, this make some assumptions that might not be true for your case. However, if you use the right locating technique for your modal dialog, you should be able to:

1. Locate the modal window (use By class to locate it)
2. Use WebDriverWait to setup your timeout conditions
3. Tell the driver to switch to it (if this times out, skip steps 3, 4, and 5)
4. Locate the checkbox and OK buttons
5. Click the checkbox and the OK button in that order
6. Tell the driver to switch back to the main window
7. Continue with your test

@Grasshopper 's answer points us to the exact modified constructor of FluentWait and your requirement of removing the deprecation warning from withTimeout and pollingEvery fields. Incase you are facing further difficulty you can use the line of code below :

import java.time.Duration;
//lines of code
Wait<WebDriver> gWait = new FluentWait<WebDriver>(pDriver).withTimeout(Duration.ofSeconds(100))
        .pollingEvery(Duration.ofMillis(600)).ignoring(NoSuchElementException.class);

You can find a detailed discussion in The type FluentWait is not generic; it cannot be parameterized with arguments error for FluentWait Class through Selenium and Java

In my Selenium IDE version 2.4.0 it is easy as pie:

1. Record testcase in Selenium IDE
2. Click File - Export Test Case As - Java / JUnit4 / WebDriver
3. Save File as .java

And here you go! Your testcase is converted to WebDriver ;)

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

Hinted by this Chromedriver ticket (about the silent option), I looked in the source of ChromeDriverService.java, and found a reference to "webdriver.chrome.logfile".

After adding -Dwebdriver.chrome.logfile="/dev/null" to my java command, the logs became readable again: The usless ChromeDriver logs were gone, while theSystem.out.println calls and exceptions are still shown in the console.

I start java with the following parameters (Linux / Mac):

DIR=path/to/dir/containing/selenium/and/stuff
cd "$DIR" && java -cp "$DIR\
:$DIR/output\
:$DIR/bin/selenium-server-standalone-2.33.0.jar" \
-Dwebdriver.chrome.driver="$DIR/bin/chromedriver" \
-Dwebdriver.chrome.args="--disable-logging" \
-Dwebdriver.chrome.logfile="/dev/null" \
AllTests

If you're on Windows:

set DIR=path\to\dir\containing\selenium\and\stuff
cd "%DIR%" && java -cp "%DIR%;%DIR%\output;%DIR%\bin\selenium-server-standalone-2.33.0.jar" ^
-Dwebdriver.chrome.driver="%DIR%\bin\chromedriver.exe" ^
-Dwebdriver.chrome.args="--disable-logging" ^
-Dwebdriver.chrome.logfile=NUL ^
AllTests

Explanation for the composition of my classpath (-cp): My tests are located in a directory at "$DIR/output". The Selenium jar file is placed in "$DIR/bin/selenium-server-standalone-2.33.0.jar". "AllTests" is the name of my class containing public static void main(String[] args) - this launches my tests.

The other parameters are self-explanatory, adjust it to your needs. For convenience (used in a shell/batch script), I've declared the common directory in a variable DIR.

You can easily accomplish this task with CSS.

The formula is:

element[attribute='attribute-value']

So if you have,

<a href="mysite.com"></a>

You can find it using:

By.cssSelector("a[href='mysite.com']");

this works using any attribute possible.

This page here gives good information on how to formulate effective css selectors, and matching their attributes: http://ddavison.io/css/2014/02/18/effective-css-selectors.html

Naif,

Actually, your above question is different than the actual question hence you should have asked it as a separate question. Still, I'm answering to your previous question.

The error is because the element you're trying to click on isn't visible. Before you click on element, it should be visible. You can do this by following -

WebElement element = driver.findElement(By.xpath("//div[2]/div[2]"));
WebDriverWait wait = new WebDriverWait(driver, 20); //here, wait time is 20 seconds

wait.until(ExpectedConditions.visibilityOf(element)); //this will wait for elememt to be visible for 20 seconds
element.click(); //now it clicks on element

If above doesn't work, you can click on element by executing javascript(but this isn't a good practice)

JavascriptExecutor js = (JavascriptExecutor)driver;
js.executeScript("arguments[0].click();", element);

Google shrinks their css classes etc., so it is not easy to identify everything.

Also you have the problem that you have to "wait" until the site shows the result. I would do it like this:

public static void main(String[] args) {

    WebDriver driver = new FirefoxDriver();
    driver.get("http://www.google.com");
    WebElement element = driver.findElement(By.name("q"));
    element.sendKeys("Cheese!\n"); // send also a "\n"
    element.submit();

    // wait until the google page shows the result
    WebElement myDynamicElement = (new WebDriverWait(driver, 10))
              .until(ExpectedConditions.presenceOfElementLocated(By.id("resultStats")));

    List<WebElement> findElements = driver.findElements(By.xpath("//*[@id='rso']//h3/a"));

    // this are all the links you like to visit
    for (WebElement webElement : findElements)
    {
        System.out.println(webElement.getAttribute("href"));
    }
}

This will print you:

• http://de.wikipedia.org/wiki/Cheese
• http://en.wikipedia.org/wiki/Cheese
• http://www.dict.cc/englisch-deutsch/cheese.html
• http://www.cheese.com/
• http://projects.gnome.org/cheese/
• http://wiki.ubuntuusers.de/Cheese
• http://www.ilovecheese.com/
• http://cheese.slowfood.it/
• http://cheese.slowfood.it/en/
• http://www.slowfood.de/termine/termine_international/cheese_2013/

Your assumption "... ExpectedConditions.visibilityOf(WebElement) would find the first element visible." is wrong! You will need to declare your WebElement as a List, find all of them, and pick the one that is visible. Here is a sample that I used successfully in the past:

@FindBy(xpath = "//input[@ng-model='loginData.username']")
private List<WebElement> txtUsername;

public String getUsername() {
    driverWait.until(CustomExpectedConditions.presenceOfAllElements(txtUsername));
    for (WebElement oneUsername : txtUsername) {
        if (oneUsername.isDisplayed())
            return oneUsername.getAttribute("value");
    }
    return null;
}

public void setUsername(String username) {
    driverWait.until(CustomExpectedConditions.presenceOfAllElements(txtUsername));
    for (WebElement oneUsername : txtUsername) {
        if (oneUsername.isDisplayed()) {
            oneUsername.clear();
            oneUsername.sendKeys(username);
            break;
        }
    }
}

Based on discussion elsewhere, here is the CustomExpectedConditions:

public class CustomExpectedConditions {
    /**
     * Based on {@link ExpectedConditions#presenceOfAllElementsLocatedBy(org.openqa.selenium.By)}.
     * 
     * @param elements
     * @return
     */
    public static ExpectedCondition<List<WebElement>> presenceOfAllElements(
            final List<WebElement> elements) {
        return new ExpectedCondition<List<WebElement>>() {

            @Override
            public List<WebElement> apply(WebDriver driver) {
                // List<WebElement> elements = findElements(locator, driver);
                return elements.size() > 0 ? elements : null;
            }
        };
    }
}