You have to pin your loggers in memory or setup a logging.properties config file. From the java.util.logging.Logger docs:

Logger objects may be obtained by calls on one of the getLogger factory methods. These will either create a new Logger or return a suitable existing Logger. It is important to note that the Logger returned by one of the getLogger factory methods may be garbage collected at any time if a strong reference to the Logger is not kept.

When a new logger is returned the log level is determined by the LogManager which by default uses settings from a logging.properties file. In your example, it is possible to see the following:

1. Call to getLogger creates a new logger and sets level from LogManager.
2. Your code sets the logger level to OFF.
3. G.C. runs and destroys your logger along with settings you just applied.
4. Selenium calls getLogger and creates a new logger and sets level from LogManager.

Here is an example test case to prove the point:

    public static void main(String[] args) {
        String name = "com.gargoylesoftware.htmlunit";
        for (int i = 0; i < 5; i++) {
            System.out.println(Logger.getLogger(name).getLevel());
            Logger.getLogger(name).setLevel(Level.OFF);
            System.runFinalization();
            System.gc();
            System.runFinalization();
            Thread.yield();
        }
    }

Which will output null instead of OFF.

If you pin your logger by holding a strong reference then step #3 never happens and Selenium should instead find the logger you created which has the level set to OFF.

private static final Logger[] pin;
static {
    pin = new Logger[]{
        Logger.getLogger("com.gargoylesoftware.htmlunit"),
        Logger.getLogger("org.apache.commons.httpclient"),
        Logger.getLogger("org.openqa.selenium.remote.ProtocolHandshake")
    };

    for (Logger l : pin) {
        l.setLevel(Level.OFF);
    }
}

First of all you need to import the proper drivers into the project/class.

like

import org.openqa.selenium.firefox.FirefoxDriver;
import org.openqa.selenium.chrome.ChromeDriver;
import org.openqa.selenium.ie.InternetExplorerDriver;

etc.

The you need to create new Webdrivers for the broswer you need.

like

WebDriver driver = new FirefoxDriver();
WebDriver driver = new InternetExplorerDriver();
WebDriver driver = new ChromerDriver();

etc for each browser.

NOTE: It is tough to use different browsers/drivers in a single test. Either you may use similar tests for each browser and maintain a test-suite (i.e. use one driver and import in a test and maintain similar test for other browsers) or you can use some config files or excel to pick up which browser you want the test to run. You might like to explore http://htmlunit.sourceforge.net/ for headless testing.

And information about OperaDriver can be found here: - https://github.com/operasoftware/operadriver/

The problem with using getPageSource(), is there could be id's, classnames, or other parts of the code which match your String, but those don't actually appear on the page. I suggest just using getText() on the body element, which will only return the page's content, and not HTML. If I'm understanding your question correctly, I think that is more what you are looking for.

// get the text of the body element
WebElement body = driver.findElement(By.tagName("body"));
String bodyText = body.getText();

// count occurrences of the string
int count = 0;

// search for the String within the text
while (bodyText.contains("VIM LIQUID MARATHI")){

    // when match is found, increment the count
    count++;

    // continue searching from where you left off
    bodyText = bodyText.substring(bodyText.indexOf("VIM LIQUID MARATHI") + "VIM LIQUID MARATHI".length());
}
System.out.println(count);

The variable count contains the number of occurrences.

As Florent B. has commented, the old selenium-java-x.xx.x.jar was renamed to client-combined-x.x.x-nodeps.jar. The new name of the JAR was not very obvious.

Simply add this new JAR in your build path Libraries.

This error message...

ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.

...is a common Google Chrome error when trying to run it in Linux due to Chrome’s GPU usage.

First of all, System.setProperty() line accepts the key webdriver.chrome.driver and the value of the absolute path of the ChromeDriver. So instead of:

System.setProperty("webdriver.chrome.driver", "/usr/bin/google-chrome");

You need to:

System.setProperty("webdriver.chrome.driver", "/path/to/chromedriver");

Outro

Generally this error can be addressed by avoiding the GPU hardware acceleration with the following flags:

• --disable-gpu: Disables GPU hardware acceleration. If software renderer is not in place, then the GPU process won't launch
• --disable-software-rasterizer: Disables the use of a 3D software rasterizer

Code snippet:

options.addArguments("--disable-gpu");
options.addArguments("--disable-software-rasterizer");

A Regular refresh may reload the page from its cache.

A Hard refresh reloads from the server, not from cache.

If you wish to delete the Cache too use Cache.delete():

see MDN Web Docs on Cache.delete().

The answer:

You can use location.reload(true); with execute_script:

driver.execute_script("location.reload(true);")

Reloads the resource from the current URL. Its optional unique parameter is a Boolean, which, when it is true, causes the page to always be reloaded from the server. If it is false or not specified, the browser may reload the page from its cache.

For more info see MDN Web Docs on Location.

Hope this helps!

If you are on Java-8 you can run a parallel for loop using aparallelStream

 IntStream.range(0,20).parallel().forEach(i->{
         ... do something here
 });

To get list of links use driver.findElements(By.tagName("a")) and then to select one at random use a random number generator and select the WebElement at the array index.

http://docs.seleniumhq.org/docs/03_webdriver.jsp

Many GWT elements comes with ensureDebugId (method on UIObject) to allow you to explicitly set Ids to elements for testing and debugging purpose. You also need to inherit the module

 <inherits name="com.google.gwt.user.Debug"/> 

to make it work. The advantage of this is, you can remove the trace from the production deployment by removing the inherited module in during prod mode compile. Hence there wont be code changes to remove unnecessary Ids.