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

Use full resource ID ...It worked for me....

below line worked for me.... driver.findElement(MobileBy.id("com.android.packageinstaller:id/permission_allow_button")).click();

Here's a couple of reasons off the top of my head:

1) You can hook your selenium tests into your build process (and hence your CI process).

2) You can use JUnit assertions.

3) You can build up multiple suites of JUnit tests (which can then be run in parallel).

I'm sure there's more but I guess it depends on the number of tests you have and the size of the project you are working on. If you're project already has a set of JUnit tests then it's quite nice to be able to write selenium tests without too much effort.

The following might help your requirement. In the following code, we override apply method incorporating the condition that we are looking for. So, as long as the condition is not true, in our case, the enabled is not true, we go in a loop for a maximum of 10 seconds, polling every 500 ms (this is the default) until the apply method returns true.

WebDriverWait wait = new WebDriverWait(driver,10);

wait.until(new ExpectedCondition<Boolean>() {
    public Boolean apply(WebDriver driver) {
        WebElement button = driver.findElement(By.xpath("xpath"));
        String enabled = button.getAttribute("aria-disabled");
        if(enabled.equals("true")) 
            return true;
        else
            return false;
    }
});

By default, a completely clean profile with an empty cache, local storage, cookies is fired up by selenium. You are actually browsing privately with selenium.

First of all, there is a problem in your code - you are not passing your DesiredCapabilities instance to the webdriver constructor (not tested though):

ChromeDriver driver = new ChromeDriver(capabilities);

You may also try forcing the "incognito" mode:

DesiredCapabilities capabilities = DesiredCapabilities.chrome();

capabilities.setCapability(CapabilityType.ForSeleniumServer.ENSURING_CLEAN_SESSION, true);
capabilities.setCapability("chrome.switches", Arrays.asList("--incognito"));

ChromeDriver driver = new ChromeDriver(capabilities);

As far as I know, there are 3 ways:

1. Implicit wait: (It's applicable for all elements on the page)

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

2. Explicit wait: (Applicable for a particular element)

   WebDriverWait.until(CONDITION_THAT_FINDS_AN_ELEMENT);

More specific code is as below:

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

1. Using Thread:

   Thread.sleep(NUMBER_OF_MILLIS);

You can try this one too as CSS Selector

driver.findElement(By.cssSelector("input[type='button'][value='Open device access']")).click();

or

driver.findElement(By.cssSelector("input[type='button']")).click();

I had the same issue, my mistake was because i was making driver.get("localhost:...") instead of driver.get("http://localhost:...")

You can do it by using Chrome DevTools Protocol, and here is the python code:

driver = webdriver.Chrome()
tz_params = {'timezoneId': 'America/New_York'}
driver.execute_cdp_cmd('Emulation.setTimezoneOverride', tz_params)

After digging a little deeper, I came to the following findings which eventually solved my issue:

1. Marionette resp. wires uses two ports (see wires --help); a marionette-port and a webdriver-port:

   Usage:
       ./wires [OPTIONS]
   
   WebDriver to marionette proxy.
   
   optional arguments:
     -h,--help             show this help message and exit
     -b,--binary BINARY    Path to the Firefox binary
     --webdriver-host WEBDRIVER_HOST
                           Host to run webdriver server on
     --webdriver-port WEBDRIVER_PORT
                           Port to run webdriver on
     --marionette-port MARIONETTE_PORT
                           Port to run marionette on
     --connect-existing    Connect to an existing firefox process
   

   When running multiple MarionetteDrivers simultaneously, both ports have to be different from the already running instance obviously. However, when using the default constructor new MarionetteDriver() the marionette-port remains constant (and is not determined based on some free port). We used some workaround (see below) for the GeckoDriverService.Builder to always pick two randomly-chosen available ports.

2. The current (version 2.48.2) GeckoDriverService has an empty implementation of waitUntilAvailable() (which should check, if the WebDriver is ready to go). Sporadically, this lead to the UnreachableBrowserException posted above.

To circumvent these issues, we did something like this at the end:

// determine free ports for Marionette and WebDriver
final int marionettePort = PortProber.findFreePort();
final int webDriverPort = PortProber.findFreePort();
// override, as GeckoDriverService provides no direct way to set the Marionette port
GeckoDriverService.Builder builder = new GeckoDriverService.Builder() {
    @Override
    protected ImmutableList<String> createArgs() {
        Builder<String> argsBuilder = ImmutableList.builder();
        argsBuilder.addAll(super.createArgs());
        argsBuilder.add(String.format("--marionette-port=%d", marionettePort));
        return argsBuilder.build();
    }
};
builder.usingPort(webDriverPort);
builder.usingDriverExecutable(pathToDriver);
GeckoDriverService driverService = builder.build();
try {
    driverService.start();
} catch (IOException e) {
    throw new IllegalStateException("Could not start the GeckoDriverService", e);
}
try {
    // keep checking the WebDriver port via Socket until it's available;
    // as far as I could tell, there is nothing more "high level", e.g. REST API
    waitUntilReady(webDriverPort, TimeUnit.SECONDS.toMillis(30));
} catch (InterruptedException e) {
    // ignore
}
return new MarionetteDriver(driverService, capabilities);