Click Here To View The Official Schedule
Click here to register for Track B on Tuesday, April 5
Keynote Speakers

Jason Huggins
Co-Founder of Sauce Labs; Co-Creator of Selenium
Jason Huggins co-founded Sauce Labs and is the resident “crazy idea guy”. Actually, his official title is “Executive Software Chef”. Prior to Sauce Labs, Jason was a Test Engineer at Google where he supported the grid-scale “Selenium Farm” for testing Google applications such as Gmail and Google Docs. Jason’s experience also includes time at ThoughtWorks in Chicago as a software developer. While at ThoughtWorks, Jason created the Selenium testing tool out of the need to cross-browser test a new in-house time and expense system. When not programming in Python or JavaScript, Jason enjoys hacking on Arduino-based electronics projects. Jason has spent time in New York City, LA, and the Bay Area, but Chicago is his kind of town.

Patrick Lightbody
Director of Product Management at Webmetrics; Founder of BrowserMob
Patrick joined Neustar Webmetrics as the Director of Product Management after his startup, BrowserMob, was acquired in July 2010. BrowserMob provides low-cost, self-service, cloud-based products that help monitoring and test the performance of modern web sites. Patrick is an avid open source contributor, having founded OpenQA, developed Selenium Remote Control, and co-created Struts 2. Prior to founding BrowserMob, he was the senior Product Manager at Gomez, running the QA Solutions product group. Before that, he founded HostedQA, an automated web-testing platform acquired by Gomez in 2007. Patrick has held management and software engineering positions with Jive Software, Spoke Software, and Cisco Systems.

Bret Pettichord
Staff QA Engineer at Convio; Lead Developer of Watir
Bret Pettichord is a quality assurance engineer at Convio and the director of the Watir project. He co-authored ‘Lessons Learned in Software Testing’, co-founded Watir and was on the launch team for Selenium.

Simon Stewart
Senior Software Engineer at Google; Creator of Selenium 2
Simon Stewart lives in London and works as a Software Engineer in Test at Google. His Open Source contributions centre on Selenium, where he’s one of the noisier members of the community and a core contributor to the project. It has been said before that Simon enjoys beer and writing better software, sometimes at the same time. This is true. He is also the top hit for the search term “steel cage knife fight”, a fact that makes in inordinately proud
Conference Speakers

Dante Briones
Principal Consultant at Electronic Ingenuity
The Page Object pattern is a powerful way to organize your test code that promotes ease of writing new tests and maintenance of existing ones. But as web applications have become more and more powerful, it’s become increasingly difficult to model their UIs as a collection of monolithic “pages”. In this talk, I’ll show you a technique that I’ve used to write tests for complex web applications that preserves all the benefits of Page Objects. I’ll cover the underlying concepts of my approach and share solutions for some of the related issues you’re likely to encounter while testing a modern web application, like how to deal with dynamic page content.

Adam Christian
JavaScript Architect at Sauce Labs
When it comes to web application automation, there are a lot of people out there who do just enough to make it work so that they can get on with their day. However, if you had all day to work on this full time, you would wind up with some pretty great tips, tricks and realizations that would make your life exponentially easier. Additionally, every automation and QA setup is totally different and the way you go about picking tools and tailoring them to your setup will either make you a rock star, or quite the opposite. Spend a few minutes learning some of the available tips and tricks that could save you some agony — especially for users who haven’t done this before.

Kevin Evans
Director of QA at Concur
Concur has a heavy reliance on Selenium automation. Within the next six months, we will achieve a 1 million execution per month milestone. What makes Concur’s Selenium usage somewhat unique is that the majority of the automation scripts are in Selenese/HTML utilizing the TestRunner.The primary focus of this talk will be to convey some of the lessons that we have learned along the way, to share some the simple but effective methods that we have come to rely upon, and to discuss the future plans for the Concur automation efforts.

Adam Goucher
Maintainer of Selenium IDE; Principal at Element 34
Selenium IDE is pretty much ‘feature complete’ in terms of a record-and-playback editor. Its future development and customization lies in the development of plugins. In this talk, I’ll show what you can do with the existing Plugin API, give a peek into the future of it and explain why less ‘in the editor’ is better for the long term success of Selenium IDE.

Shane Hender
Software Engineer at Neustar
Mark Watson
Software Engineer at Neustar
The goal of this talk is to help you build a performance testing framework for your web application in under a day. We will show how to enhance Selenium with tools such as Fiddler and the new Web-Timings standards (as supported in IE9, Firefox 4, and Chrome) that can be used to gather performance metrics. With web performance being critically important, organizations need to adopt performance monitoring as early as possible in their development life-cycle. Performance engineers and Operations require this data to monitor potential problems and the current state of the system, while developers and QA need this information to prevent regressions and get instant feedback on any code changes.

Jez Humble
Product Manager at ThoughtWorks
Getting software released to users is often a painful, risky, and time-consuming process. This talk sets out the principles and technical practices that enable rapid, incremental delivery of high quality, valuable new functionality to users. Through automation of the build, deployment, and testing process, and improved collaboration between developers, testers and operations, delivery teams can reduce cycle times and improve the quality of their software and the reliability of the release process.


Dave Hunt
QA Engineer at Mozilla
Andy Smith
Senior Web Developer at AKQA
Despite recent improvements to automated testing tools, there’s still a large gap when it comes to emerging technologies such as HTML5. Recent developments like the canvas element present an interesting dilemma for traditional automated testing as they expose little or no information to debug tools. In order to move forwards, both developers and testers will need to work together. Using Selenium, Java, and JavaScript we will demonstrate writing automated tests for a popular canvas game.

Joel Klabo
Software Engineer at Yammer
If you are building a Flex website and looking for a way to automate your testing, you should know about FlexPilot. In this talk, I will go over the fundamentals of Flex testing automation with Selenium and FlexPilot and explain basic setup. Additionally, I’ll show a demo of FlexPilot working on various Flex components, while telling how to add support for unsupported or partially supported components.

Dima Kovalenko
QA at Groupon
Wouldn’t it be nice to have the BA’s write out the acceptance criteria in plain English, and then have those criteria run as tests? Join us for a beginner to intermediate walk through of Cucumber and Selenium. Learn how to write tests that are easy to understand and run. There will be plenty of examples and sample code to get you going in the right direction.

Eran Messeri
Software Engineer in Test at Google
As an alternative to the traditional Selenium Grid approach, browser instances for Selenium tests can be provided on virtual machines in a clean, consistent state. While the approach itself isn’t new, making such an infrastructure is tricky – especially when dealing with large amounts of tests across multiple platforms. In this talk, I’ll present the infrastructure built at Google to provide a web-testing platform that enables large-scale browser-based tests.

Mikeal Rogers
Developer Advocate at Yammer
This is an overview of some work that I did at Mozilla about a year ago. Tests generate lots of data. And different tests generate different kinds of data. I’ll talk about taking large amounts of test data and sticking it in to CouchDB. I’ll answer questions such as: Is this failure a new failure? How many “random” failures do we have? And what platform shows the least reliable results?


Kevin Menard
Maintainer of Selenium Grid; Founder of MogoTest
Francois Reynaud
Senior Software Quality Engineer at ebay
Selenium Grid is the standard means of organizing a cluster of browsers in a test environment, allowing a test suite to target particular browsers, versions, and platforms. Until recently Selenium Grid was only compatible with the older Selenium 1 RC. In this talk we introduce the new Selenium Grid 2, improvements over the older grid, and how to use it with Selenium 2.

Andy Tinkham
Senior QA Analyst at Healthland
This talk presents a case study of the automation infrastructure we are building at Healthland. This infrastructure uses Cucumber for plain text test definition and Selenium RC 2 to control the web browsers we test against. Our code utilizes the concepts of page objects to help minimize the maintenance required. We’ll also talk about our planned future enhancements for our test framework.

Andreas Tolf Tolfsen
QA Engineer at Opera Software
OperaWatir is new to the Watir- and Selenium families of testing toolkits, and finally brings automated testing to any device. I will be showing off OperaWatir’s new jQuery-like querying engine and give practical examples of strategies on testing web browsers at Opera. At Opera, the situation is turned upside down. Instead of using the browser for testing web applications, we use web pages to test the browser. The talk will give you a broad introduction to how we test web browsers and why emulating actual user behaviour is quintessential to the success of your testing.