I arrived at Google’s London HQ (or Googleplex) at 18:00 to meet with Eran and Simon – who was only around thanks to the cloud of volcanic ash preventing him from flying out to New York! After a quick tour of the offices, and a brief label-off (I lost) people started to arrive. They were early – definitely a good sign!

I was the first to present, and I’m not used to speaking in-front of an audience, but my preparation and practise paid off as I feel my presentation went well. My talk covered a suggested migration path from Selenium IDE to Selenium 2 using my WebDriver Backed Formatters plugin for IDE, and contained live demos. After a few questions my presentation was over and I could relax!

David Burns next took to the stage with his presentation on what Selenium 2 means to the average QA. There was a short delay in getting started (which I understand we’re blaming Eran for, but might be more to do with David not using a Macbook ). Before long David’s talk was under way. Of particular interest were the demos, where by simply switching a test to use Selenium 2 he solved one of the most irritating limitations of Selenium 1 – typing into a rich text editor! This was followed by solving another limitation, with a demo that entered a file name into a <input type=”file”> field. After a few more questions for both David and Simon, the second presentation came to an end.

After our final break Eran gave a short presentation of his current work on an advanced user interactions API, which is something I’m looking forward to for testing complex Ajax applications with rich interfaces. The idea being that you can combine several actions such as ‘Hold shift, click down on element X, and drag it onto element Y’. Also mentioned was the mobile (or ‘Fingers’) interactions API to support swiping, pinching, etc. A very good talk, and proof (if needed) that Google are taking the future of Selenium very seriously – there’s a lot of work going into it!

Earlier on in the evening Simon had asked for questions to be written on the whiteboard, and instead of his planned talk – which he’d mostly given all of the details out as answers to questions throughout the evening – he worked his way through the list. The questions included: testing Ajax applications using Selenium 2 (you can), is the Selenium IDE dead (no), is Selenese dead (not quite), and does Selenium Grid support Selenium 2 (not yet).

After the Q&A it there was just time for some more refreshments, but then I had to then start my journey home. I hear those that stayed had some lively discussions in the nearby pub about dynamic Firefox instances and the like, with Google buying everyone one more beer!

Feedback on the event has so far been very positive, and I’d like to thank everyone that came along – there were some interesting questions, and a good range of Selenium experience in the room.

It was a thoroughly enjoyable event and I’d like to thank Google for being such awesome hosts, Simon for all of his efforts and question answering, Eran Messeri for his great work on the project and for sharing some of that with us, and David Burns for his presentation and demos.

I would also like to thank Jérémy Hérault (Selenium committer) and Kévin Pollet (creator of Helium plugin for Selenium IDE) for coming along – they were travelling for 8 hours to get to the event and had to do a return journey the same day! I hope it hasn’t put you off coming to future events guys!

Slides, notes, demos, videos (possibly), all to follow!

This is quite possibly the most exciting development in Selenium IDE in a long time, and the best thing is that it enables users to come up with their own improvements – in much the same way as Greasemonkey or Firefox addons themselves. The possibilities are endless.

Adam Goucher continues to post guidance on creating plugins on his blog as the API evolves. I have followed these myself to create two plugins:

• Flow control – This is actually just an old Selenium user extension that I’ve repackaged into a plugin. Two main advantages of doing this are: an easy install/disable/uninstall process, and no messing around with JavaScript files! [install] [public repository]
• WebDriver Backed Selenium Formatters – This is a formatter plugin that provides the Selenium emulation from WebDriver, giving quick access to WebDriver’s advantages without changing from the existing Selenium API. [install] [public repository]

These plugins are available to download from SeleniumExamples, and you can view the source/report issues/provide feedback via the GitHub repositories.

Let SeleniumExamples know if you’re developing your own plugin, or have any good ideas. I’ll be happy to review, host, or link to your plugins – most of all we want to encourage plugin development.

Update:
Plugins now made available via addons.mozilla.org:

• Flow Control
• WebDriver Backed Selenium Formatters

WebDriverTestBase.java

package tests;
 
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.firefox.FirefoxDriver;
import org.openqa.selenium.support.ui.Wait;
import org.openqa.selenium.support.ui.WebDriverWait;
import org.testng.Assert;
import org.testng.annotations.AfterClass;
import org.testng.annotations.BeforeClass;
 
public class WebDriverTestBase {
 
	public static FirefoxDriver driver;
	public static Wait wait;
 
	@BeforeClass(alwaysRun = true)
    protected void startWebDriver() {
    	driver = new FirefoxDriver();
    	wait = new WebDriverWait(driver, 120);
    }
 
    @AfterClass(alwaysRun = true)
    protected void closeSession() {
	    driver.close();
    }
 
    public static void assertEquals(Object actual, Object expected) {
    	Assert.assertEquals(actual, expected);
    }
 
}

VisibilityOfElementLocated.java

package tests;
 
import org.openqa.selenium.By;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.support.ui.ExpectedCondition;
 
public class VisibilityOfElementLocated implements ExpectedCondition {
 
	By findCondition;
 
	VisibilityOfElementLocated(By by) {
		this.findCondition = by;
	}
 
	public Boolean apply(WebDriver driver) {
		driver.findElement(this.findCondition);
		return Boolean.valueOf(true);
	}
 
}

WebmailTest.java

package tests;
 
import org.openqa.selenium.By;
import org.testng.annotations.Test;
 
public class WebmailTest extends WebDriverTestBase {
 
	//variables
	public static final String YAHOO_EMAIL = "example@yahoo.co.uk";
	public static final String HOTMAIL_EMAIL = "example@hotmail.co.uk";
 
	@Test(description = "Sends an e-mail from Yahoo account")
	public void sendFromYahoo() {
		//new message variables
		String to = HOTMAIL_EMAIL;
		String subject = "Test Sending Email Message From Yahoo";
		String message = "This is a test e-mail from Yahoo";
 
		//login to yahoo
		driver.get("http://mail.yahoo.com/");
		driver.findElement(By.id("username")).sendKeys(YAHOO_EMAIL);
		driver.findElement(By.id("passwd")).sendKeys("mytestpw");
		driver.findElement(By.id(".save")).click();
 
		//create new message
		driver.findElement(By.id("compose_button_label")).click();
		wait.until(new VisibilityOfElementLocated(By.xpath("id('_testTo_label')/ancestor::tr[1]//textarea")));
 
		//send test message
		driver.findElement(By.xpath("id('_testTo_label')/ancestor::tr[1]//textarea")).sendKeys(to);
		driver.findElement(By.xpath("id('_testSubject_label')/ancestor::tr[1]//input")).sendKeys(subject);
		driver.switchTo().frame("compArea_test_");
		driver.findElement(By.xpath("//div")).sendKeys(message);
		driver.switchTo().defaultContent();
		driver.findElement(By.id("SendMessageButton_label")).click();
		//WARNING! sometimes a captcha is displayed here
		wait.until(new VisibilityOfElementLocated(By.xpath("//nobr[contains(text(), 'Message Sent')]")));
	}
 
	@Test(description = "Sends an e-mail from Hotmail account")
	public void sendFromHotmail() {
		//new message variables
		String to = YAHOO_EMAIL;
		String subject = "Test Sending Email Message From Hotmail";
		String message = "This is a test e-mail from Hotmail";
 
		//login to hotmail
		driver.get("http://mail.live.com/");
		driver.findElement(By.name("login")).sendKeys(HOTMAIL_EMAIL);
		driver.findElement(By.name("passwd")).sendKeys("mytestpw");
		if (driver.findElement(By.name("remMe")).isSelected()) {
			driver.findElement(By.name("remMe")).click();
		}
		driver.findElement(By.name("SI")).click();
 
		//create new message
		driver.switchTo().frame("UIFrame");
		driver.findElement(By.id("NewMessage")).click();
 
		//send test message
		driver.findElement(By.id("AutoCompleteTo$InputBox")).sendKeys(to);
		driver.findElement(By.id("fSubject")).sendKeys(subject);
		driver.switchTo().frame("UIFrame.1");
		driver.findElement(By.xpath("//body")).sendKeys(message);
		driver.switchTo().frame("UIFrame");
		driver.findElement(By.id("SendMessage")).click();
		assertEquals(driver.findElement(By.cssSelector("h1.SmcHeaderColor")).getText(), "Your message has been sent");
	}
 
}

Disclaimer: These tests are working at the time of this post but do require active e-mail accounts. They are likely to fail when the web based e-mail clients update their applications. Also, please don’t misuse these examples – their intention is to show how to use the WebDriver API and were inspired by a test assignment for an interview process.