Mobile & Web Functional Automation and Performance Testing.: October 2014

Wednesday, October 8, 2014

Mobile Emulation in ChromeDriver 2.11

ChromeDriver 2.11 release has the mobile emulation support using Chrome Dev Tools. I have been waiting for this feature since long.

This is how we can emulate different devices using the Java code.

import java.util.HashMap;
import java.util.Map;

import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;
import org.openqa.selenium.chrome.ChromeOptions;
import org.openqa.selenium.remote.DesiredCapabilities;


public class MobileEmulation {
 static DesiredCapabilities  capabilities;
 static String DeviceName;
 public static void main(String[] args) {
  //some Sample Devices. Complete list can be found here: https://code.google.com/p/chromium/codesearch#chromium/src/chrome/test/chromedriver/chrome/mobile_device_list.cc
  //pick any of the device
  
//  DeviceName = "Google Nexus 5";
//  DeviceName = "Samsung Galaxy S4";
//  DeviceName = "Samsung Galaxy Note 3";
//  DeviceName = "Samsung Galaxy Note II";
//  DeviceName = "Apple iPhone 4";
  DeviceName = "Apple iPhone 5";
//  DeviceName = "Apple iPad 3 / 4";

  String ChromeDriverPath = System.getProperty("user.dir") + "/lib/chromedriver.exe";
  System.setProperty("webdriver.chrome.driver", ChromeDriverPath);
  
  Map<String, String> mobileEmulation = new HashMap<String, String>();
  mobileEmulation.put("deviceName", DeviceName);
  
  Map<String, Object> chromeOptions = new HashMap<String, Object>();
  chromeOptions.put("mobileEmulation", mobileEmulation);

  capabilities = DesiredCapabilities.chrome();
  capabilities.setCapability(ChromeOptions.CAPABILITY, chromeOptions);
  WebDriver driver = new ChromeDriver(capabilities);
  
  driver.manage().window().maximize();
  driver.navigate().to("http://www.google.com");

 }

}

Tuesday, October 7, 2014

Quick Tips on ChromeDriver - Part 1

To Change the default download directory in chrome using WebDriver Java Bindings and ChromeDriver.

ChromeOptions options=new ChromeOptions();
DesiredCapabilities  capabilities = DesiredCapabilities.chrome();
Map<String, Object> prefs = new HashMap<String, Object>();
prefs.put("profile.default_content_settings.popups", 0);
prefs.put("download.default_directory", "D:\\downloads");
prefs.put("savefile.default_directory", "D:\\downloads");
options.setExperimentalOption("prefs", prefs);
capabilities.setCapability(ChromeOptions.CAPABILITY, options);
WebDriver driver = new ChromeDriver(capabilities);

To Use a custom profile in ChromeDriver which can be utilized for many use cases:

      ChromeOptions options=new ChromeOptions();
      DesiredCapabilities  capabilities = DesiredCapabilities.chrome();
      chromeoptions.addArguments("user-data-dir="+chromeprofilepath);
      capabilities.setCapability(ChromeOptions.CAPABILITY, options);
      WebDriver driver = new ChromeDriver(capabilities);

Capturing Network Traffic Generated by Eclipse IDE

To Capture the network traffic generated by Eclipse IDE, you just need to place the following code where we are passing the proxy host and port on which your proxy tool is running.

We can use any of the proxy tool like Charlesproxy or Fiddler to do this.

System.setProperty("http.proxyHost", "IP or Hostname");
System.setProperty("http.proxyPort", "8888");
System.setProperty("https.proxyHost", "IP or Hostname");
System.setProperty("https.proxyPort", "8888");

Sunday, October 5, 2014

MY UNFORGETTABLE JOURNEY TO SELENIUM CONFERENCE 2014

I can still remember when I heard the word ‘Selenium’ for the first time from one of my colleagues while working at Oracle. My instant reaction was that it was some chemical and after some Googling, I realized I was right. It was only after a couple of days that I came to know from the same colleague that what he meant from the word “Selenium” was not a chemical but the open-source functional automation tool.

After further doing some research I found out that the gentleman who created Selenium thinks that it is better than Mercury QTP tool and that’s the reason he named it Selenium (which poisons mercury). I was taken aback when I first heard this but later decided to learn and master this tool, a step which if I had not taken would have ruined my chances to progress in the existing job. It was this decision that my journey to learning Selenium got started.

Amit Rawat (far right) on stage taking questions from the audience at the SeConf 2014.

After working for five years on this tool, one day I came to know that the 4th Selenium Conference would be held for the first time in India and I had the opportunity to represent my company at this conference. It was certainly a dream come true for someone who is an avid learner of Selenium. I thought I would make the most out of this opportunity by sharing my knowledge, which I gathered over the years on this tool. I proposed a session to speak at the conference on testing responsive web applications using Appium and the WebDriver API. Even though my proposal wasn’t selected, I was happy with the fact that I managed to get 27 likes on the idea.

After much anticipation, it was finally D-Day for the conference, which started with long queues at the registration desk. There must have been around 400 other attendees representing more than 100 different companies in this event. Keynote SeConf2014

Day 1 started with the keynote presented by the “man himself” Simon Stewart, who created Selenium WebDriver. It was an amazing experience to see him in-person and to hear him discuss the future roadmap of Selenium. A few important announcements made in the keynote were:

Selenium RC would not be part of the upcoming release of Selenium 3.0. So this was a final call and warning to all the people to upgrade from RC to WebDriver.
Selenium 3.0 will standardize the API by coming up with a well-defined W3 Spec after which all browsers implementation will follow. So it would definitely make developers’ lives easier by using the same approach across all browsers.
Selenium 3.0 will have no support for mobile browsers and the alternative solutions like Appium, iOSDriver, and Selendroid can be used for Mobile automation.

Apart from the keynote, I got a chance to attend some really good sessions. I especially liked the session presented by Jim Evans, where he showed how a company like Microsoft, whose executives used to compare open-source software to a virus, has changed its mindset in no time. Now the same company has started contributing to open-source projects like Selenium by providing their own WebDriver implementationfor Internet Explorer. This change of stance clearly shows the power of the open-source movement.

Another interesting session which I personally liked was “Scaling and Managing Selenium Grid” by Dima Kovalenko, who is also one of the Selenium committers. In this session he shared minute details about Selenium Grid configurations and some best practices, like always running a single grid node on a machine. So it is always recommended to have a dedicated VM for a single browser node rather than having multiple nodes running on a powerful machine. He also shared a very useful toolcreated by him to manage Selenium Grid configurations.

During the session breaks I interacted with many other attendees including the Selenium core committee members and tried to understand how they are utilizing this wonderful tool and what improvements they want to see in this tool. I got some amazing ideas during those interactions and I would surely like to try them in due course.

The biggest moment of the conference for me came when the Fish Bowl session started and I got the privilege to share the dais with the Selenium core committee including Simon, its founder. It was such a privilege to answer audience queries, one of which was a question related to mobile browser emulation using ChromeDriver.

Overall, it was an enriching experience for me to attend this conference, where I learnt so many new things and networked with the Selenium community.