How to use NullContext class of org.openqa.selenium.remote.tracing.empty package

I assume it is something in the lines of:

import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;
import org.openqa.selenium.logging.LogEntries;
import org.openqa.selenium.logging.LogEntry;
import org.openqa.selenium.logging.LogType;
import org.openqa.selenium.logging.LoggingPreferences;
import org.openqa.selenium.remote.CapabilityType;
import org.openqa.selenium.remote.DesiredCapabilities;
import org.testng.annotations.AfterMethod;
import org.testng.annotations.BeforeMethod;
import org.testng.annotations.Test;

public class ChromeConsoleLogging {
    private WebDriver driver;


    @BeforeMethod
    public void setUp() {
        System.setProperty("webdriver.chrome.driver", "c:\\path\\to\\chromedriver.exe");        
        DesiredCapabilities caps = DesiredCapabilities.chrome();
        LoggingPreferences logPrefs = new LoggingPreferences();
        logPrefs.enable(LogType.BROWSER, Level.ALL);
        caps.setCapability(CapabilityType.LOGGING_PREFS, logPrefs);
        driver = new ChromeDriver(caps);
    }

    @AfterMethod
    public void tearDown() {
        driver.quit();
    }

    public void analyzeLog() {
        LogEntries logEntries = driver.manage().logs().get(LogType.BROWSER);
        for (LogEntry entry : logEntries) {
            System.out.println(new Date(entry.getTimestamp()) + " " + entry.getLevel() + " " + entry.getMessage());
            //do something useful with the data
        }
    }

    @Test
    public void testMethod() {
        driver.get("http://mypage.com");
        //do something on page
        analyzeLog();
    }
}

Source : Get chrome's console log

Had the exact same issue with selenium/chromedriver on Codeship. I tried downgrading selenium to 2.53.1 to no avail. Verbose logging showed no helpful info, just the selenium server suddenly not starting new sessions somewhere randomly in our tests.

What appeared to work was adding the following to our test commands:

# Prevent chrome deadlock
export DBUS_SESSION_BUS_ADDRESS=/dev/null

Issue is described here: https://github.com/SeleniumHQ/docker-selenium/issues/87

It looks like there is an issue with certain docker containers which would explain it happening on a CI while locally working just fine.

DesiredCapabilities would help you to change user agent.

You can achieve this by calling these methods:

• setBrowserName(java.lang.String browserName)
• setPlatform(Platform platform)
• setVersion(java.lang.String version)

Or

• static DesiredCapabilities chrome()
• static DesiredCapabilities firefox()
• static DesiredCapabilities iphone()
• ...

More here.

You may manipulate ExpectedConditions to form a suitable complex condition. There're or(...) and urlContains(...) methods useful for your needs. Something like this:

WebDriverWait wait = new WebDriverWait(driver, timeout);
wait.until(ExpectedConditions.or(
    ExpectedConditions.urlContains("http://first.si.te/url"),
    ExpectedConditions.urlContains("http://second.si.te/url")
));

Try sendkeys!

public class TestClass 
 {
    public static void main(String[] args) {         
    File file = new File("D:\\Driver\\IEDriverServer.exe");
    System.setProperty("webdriver.ie.driver", file.getAbsolutePath());
    WebDriver driver = new InternetExplorerDriver();
    driver.get("http://jqueryui.com/slider/");

    WebElement slider = driver.findElement(By.xpath("//div[@id='slider']/a"));

    for (int i = 1; i <= "how many times you want" ; i++) {
            slider.sendKeys(Keys.ARROW_RIGHT);
        }

}


}

This error message...

org.openqa.selenium.WebDriverException: unknown error: failed to change window state to maximized, current state is normal

...implies that the ChromeDriver was unable to maximize the window state of Chrome Browser client.

---

Buggy Mac OSX ChromeDriver Replaced

After Chrome version 70 was released, some of you have reported that using ChromeDriver to maximize browser window on Mac no longer works. ChromeDriver Team have investigated this issue, and created a fix for it. ChromeDriver builds with the fix are now available at the following locations:

• If you are using Chrome version 70 (the current stable release), please download ChromeDriver version 70.0.3538.97 from https://chromedriver.storage.googleapis.com/index.html?path=70.0.3538.97/
• If you are using Chrome version 71 (the current beta release), please download ChromeDriver version 71.0.3578.33 from https://chromedriver.storage.googleapis.com/index.html?path=71.0.3578.33/

---

Snapshot of ChromeDriver Release Email

---

However, your main issue is the incompatibility between the version of the binaries you are using as follows:

• Your JDK version is 1.8.0_131 which is pretty ancient.
  • Upgrade JDK to recent levels JDK 8u181.
• Your Selenium Client version is 3.4.0 which is almost a year older.
  • Upgrade Selenium to current levels Version 3.14.0.

---

From another perspective, this issue looks like a regression issue from Feature request : ChromeDriver to support window resizing over a remote connection.

ChromeDriver v2.43 in the Release Notes have explicitly mentioned:

ChromeDriver to support window resizing over a remote connection

However, as per best practices to maximize the Chrome Browser client it is suggested to use ChromeOptions class as follows:

System.setProperty("webdriver.chrome.driver", "C:\\your_directory\\chromedriver.exe");
ChromeOptions opt = new ChromeOptions();
opt.addArguments("disable-infobars");
opt.addArguments("--start-maximized");
opt.addArguments("--disable-extensions");
WebDriver driver = new ChromeDriver(opt);
driver.get("https://google.com");

---

Reference

You can find a detailed discussion in driver.manage().window().maximize() issue with ChromeDriver 2.33

---

Update(Nov 20, 2018)

• ChromeDriver 2.44 has been released.
• ChromeDriver 2.44 supports Chrome versions 69 to 71
• This release is similar to ChromeDriver 2.43, but with additional bug fixes.
• A ChromeDriver that supports chrome 72.x is expected to be released in the early December.

Instead of class name you can use a css selector. You don't mention the tagname for the class 'current time'. I am assuming it to be input, so your css selector work be,

WebElement element = driver.findElement(By.cssSelector("input[class='current time']"));
element.click();

Edit#1 Based on html provided,

Looking at the html in your comment, it seems you have quite a few options to find the webElement. Here are your options,

WebElement element = driver.findElement(By.cssSelector("a[class='current time']"));
element.click();

or this should work too,

WebElement element = driver.findElement(By.cssSelector("a.current.time"));
element.click();

You can also use linkText since the element is link. From the html you provided, the link text is 'url'

WebElement element = driver.findElement(By.linkText("url"));
element.click();

You can also use By.partialLinkText("partial link text here");

You can also use xpath as:

WebElement element = driver.findElement(By.xpath("//a[@class='current time']"));
element.click();

OR,

WebElement element = driver.findElement(By.xpath("//a[text() = 'url']"));
element.click();

Java String(s) can't be done in single quotes. This,

By.cssSelector('[data-testing-id="data-id1"]')

Should be (escaping the double quotes),

By.cssSelector("[data-testing-id=\"data-id1\"]")

or with single quotes inside the double quotes, like

By.cssSelector("[data-testing-id='data-id1']")

File pathToBinary = new File("C:\\user\\Programme\\FirefoxPortable\\App\\Firefox\\firefox.exe");
FirefoxBinary ffBinary = new FirefoxBinary(pathToBinary);
FirefoxProfile firefoxProfile = new FirefoxProfile();       
WebDriver driver = new FirefoxDriver(ffBinary,firefoxProfile);