From my experience with a number of headless browsers, I’d say: HtmlUnitDriver: the fastest of all implementations I’ve come across, and perfect for simple, static pages, especially those without JavaScript. Any remotely complex page seems to produce problems – that’s my practical experience even if I can’t justify in detail. Perfect for testing Selenium features … Read more
Ok after 2 weeks I admit defeat and are using a workaround which works great for me at the moment. The problem: It is too difficult to port HTMLUnit to Android (or at least with my level of expertise). I am sure its a worthwhile project (and not that time consuming for experienced java programmer) … Read more
well, would try to explain differences in detail. Speaking about parallel testing, it better to use selenium grid. Basic concept of selenium RC and selenium grid. You can get into more details here Some words about selenium webDriver: The primary new feature in Selenium 2.0 is the integration of the WebDriver API. WebDriver is designed … Read more
Put this somewhere around the start of your code; it will shut its dirty mouth: LogFactory.getFactory().setAttribute(“org.apache.commons.logging.Log”, “org.apache.commons.logging.impl.NoOpLog”); java.util.logging.Logger.getLogger(“com.gargoylesoftware.htmlunit”).setLevel(Level.OFF); java.util.logging.Logger.getLogger(“org.apache.commons.httpclient”).setLevel(Level.OFF); webClient = new WebClient(bv); webClient.setCssEnabled(false); webClient.setIncorrectnessListener(new IncorrectnessListener() { @Override public void notify(String arg0, Object arg1) { // TODO Auto-generated method stub } }); webClient.setCssErrorHandler(new ErrorHandler() { @Override public void warning(CSSParseException exception) throws CSSException { // TODO … Read more