Whether you're just starting out, or are well on your way, there are more resources to dig through than you have time or know what to do with. With blogs, videos, documentation, forums, meetups, conferences, books, and mailing lists, the signal to noise ratio is all out of whack. In 30 minutes, I'll be your tour guide as I walk you through the information landscape of Selenium and show you which resources are worthwhile for your context and how to find them.

As the WWW morphed from a system of interlinked hypertext documents to an advanced application delivery platform, the requirements on the underlining technologies and the browsers implementing them changed dramatically.

To ensure correctness in behaviour and that application code works across multiple browsers, standards come equipped with test suites.  But interoperability can only be guaranteed by a more thorough testing effort.  The W3C has launched a new project called Test the Web Forward to bridge this gap, and WebDriver sits at its centrepiece.

The talk will focus on the infrastructure that is being created to run these tests, and exemplify how the WebDriver library can be utilized in a complex and untraditional test running framework.  It will also give a glance into the ongoing W3C WebDriver specification work, and where we are headed.

UI-tests are not really stable. Some sync point might be missed and tests will be red from time to time without any obvious reason. Or accidentally some focus might go away and button will not be clicked. These and other cases make automated testing results unpredictable and these results are not trusted. 

In my speech I want to share the experience how to reach reliable and reproducible results with Selenium tests. In order to reach it we should sacrifice to 100% end user emulation. The presentation is based on the real project where this idea was successful. Also more common recommendations will be given publicity.

Many challenging aspects need to be considered when running your Selenium test suite on real mobile browsers: choosing the right Selenium library, emulators vs. real devices, 24x7 local device infrastructure availability, unsupported features, pop-ups, etc. Do the benefits outweigh the effort?

We first talk about how to test effectively on mobile browsers using Selenium. The problems we have faced with mobile emulators, and why we are scrapping them in favour of a real mobile devices cloud of Selenium nodes. Then this is followed by a demo on how to execute your tests on iOS and Android devices. Learn how to set up a real mobile devices cloud from scratch; when we will also discuss how to run health checks for your cloud, and troubleshoot properly.

Our expertise comes from building a real iOS and Android device cloud for our customers, looking to get accurate results from testing - something to be had only from actual devices and not just emulators.

Writing tests for modern websites is quite tricky. And systems that have device-browser interaction, challenge test engineers even more.

In this talk I'll show how we use Clojure to solve problems of functional and integration testing for mobile and web applications, at Helpshift.

We use wrappers and libraries written in Clojure to leverage well known tools such as Calabash for Android, Appium for iOS, and Selenium WebDriver for the web.

Clojure is a powerful modern Lisp. In this talk, I hope to show how we benefit from many of its features, including fast, interactive REPL oriented development, rich set of data structures, and the power of macros.

Slides: http://www.slideshare.net/orenrubin/page-objects-presentation-selenium-conference-2014-38767492

In this talk I will walk the audience step by step at building tests using the Page Object Design Pattern, making several attempts until we reach the current recommendation. We'll see the dos, don'ts, and common pitfalls.

In this presentation I'll also cover the Page-Factory Design Pattern, and best practices for dealing with asynchronously and how to remove the deadly "random sleeps".

Our project was a classic example of Selenium gone wild! As our team embraced the test automation journey, we went crazy and implemented tons of Selenium tests, one for every permutation possible. Soon we realized our feedback cycles were delayed. Our builds were taking hours instead of minutes. And we had a set of complex, fragile tests, which resulted in a lot of false-negative scenarios and finger pointing.

At this point, our team had realized that this is not the path forward. We decided to seriously look at our Selenium tests. We pretty much moved 80% of our Se tests to lower-layers (non-GUI based) tests. And now we have the right testing pyramid on our project.

Join us, as we explain our journey (strategy, techniques, tools, mindset-change and approaches we took) through this transition.

QTP/UFT has been one of the leading Test Automation tool in the market. QTP supports a wide variety of technologies and with the recent article from Telerik - "5 hidden costs of Selenium". Is it really worth migrating to Selenium? If you think No, then think again. We recently migrated a client from QTP to Selenium, and the results was a 80% savings in execution time using one single machine. This case study will share the challenges we faced initially and how we managed a framework with high re-usability and execution

There is so much valuable data that Selenium Nodes writes into log file(s) when tests get executed on them. So much of this data is not mined for actionable intelligence.

In this session, we will show you how operating system level metrics can be combined with data from Selenium nodes to result in rich actionable intelligence that will tremendously aid in the analysis of test failures, react to test execution flakiness, and to improve your automated test resiliency.

Many a time the same locator in your automated script does not work well at all in all browsers/versions and operating systems or works but with flaky results in some browsers/versions. And then numerous hours are spent using a trial and error approach to either continue the hunt for a different locator that works across the board or build “if-browser/version-use-this-locator” kind of logic in your test scripts. 

In this session, we will show you an approach that will help you eliminate so much pain and cost from your cross browser test automation. 

In an era of highly interactive and responsive software processes where many organizations are using some form of methodology, test automation is frequently becoming a requirement for software projects. 

Many organizations are using Selenium-IDE and RC for testing softwares, In this talk we are going to talk about How we can use Selenium-webdriver to setup a Testing Suite for an application. 

We at Joomla!, have our testing suite built in Selenium-Webdriver along with PHPUnit and are using a Page-Object pattern to increase the code maintainability. We are going to talk about how one can setup a test suite and  built our own reporting tool with Graphical representation of test results using the logs.

The mobile world is growing, and it has never been easier to test applications—native, web, or hybrid—using Appium, a free, open-source implementation of the Selenium protocol for automating mobile devices. I will show how Appium, which is in active development and recently shipped version 1.0, allows developers and testers to harness all the power of the native testing frameworks provided by the mobile device manufacturers, but within the context familiar to Selenium users. 

Further, Appium provides a very good opportunity for looking at the challenges for a technology designed to automate web browsers as it moves into a new realm. I will discuss how functionality was repurposed for this new context, as well as the ways in which the protocol was extended and made more flexible in light of the the expanded use case.

As a case study in extended functionality, I will discuss the gesture API, which allows a standardized way to automate the sorts of advanced mutli-finger gestures used on modern mobile devices.

WebDriverJS and Cucumber.js are new entrants in the WebDriver eco-system and are gaining popularity by the day! These JavaScript ports for WebDriver and Cucumber enable us to test the JavaScript UI apps built using frameworks like Angular JS, Ember.JS with great ease.

The UI tests can be written in JavaScript, thereby using the same technical stack of the application and the tests seamlessly integrate with the code for continuous integration and continuous delivery.

The session is a demonstration of test framework using Cucumber.js and WebDriverJS for testing an open-source Angular JS application.

It's pretty cool to have selenium test results clear to everyone on the team. There are lots of frameworks in every language that aim to simplify test writing. But only few can provide sharp presentation of test execution output. Yandex team is working on Allure (https://github.com/allure-framework/allure-core/wiki) - an open-source framework designed to create crystal clear reports. Because of module structure it integrates easily with almost any testing tool, no matter which language you use. In my talk i will describe the basic principles and show how to integrate Allure reporting in your existing projects.

Traditionally companies built over enterprise infrastructure and practices have been hesistant to adopt new practices,framework or tools especially one which can change with a single commit on github. So was the case when mobile portfolio of one of the largest airline was developed and tested in an agile way and striving for continous delivery.

This is a story of remote-enablement and developing a sense of confidence in the drgaon to go open source and base its complete testing infrastructure on OSS.Today their Mobile testing with its own challenges posed by H/W,OS and Design guidelines is under the OSS umbrella with practices like BDD and compliance with test pyramid adopted with a scalable automation framework built on Ruby,Cucumber,Watir Webdriver and Calabash.

Microsoft. Just the name of the company alone can send some open-source software activists into fits of apoplexy. From the days when executives of the company compared open-source software to "a virus", the company has been seen as incredibly hostile to open-source software. It is surprising how much has changed over the years.

This is the story of how the Selenium project has managed its relationship with the software company, from the initial, tentative, often contentious and borderline hostile reaching out, to today's open engagement. The story is told through the prism of the Internet Explorer Driver project, with slight digressions to the .NET bindings and other Microsoft technology stacks. The journey is funny, sometimes frustrating, but always entertaining, and there may be a surprise announcement or two.

ExtJS is a web development framework used for developing next generation web based UIs. In ExtJs the object Id's are dynamic in nature, the object id's are not static everytime the object is rendered in UI. The challenge is to automate UI functionality when the objects are dynamic. Extjs does not recommend assigning static html-ids to objects for web application development.

Would like to share our experience how selenium webdriver with java has been leveraged in retrieving those dynamic Id's at run-time and perform operations on those objects. A way for test automation on an web application which is developed using ExtJS framework which generates the dynamic html-ids.

How do you user Selenium to test non-HTML UI components? By integrating Sikuli with Selenium we were able to solve this problem. In this demo, we would like to share our experience in increasing the automation scope to include non-HTML UI components with the help of Sikuli.

Typically learning new tools to increase automation coverage is a challenge for Selenium users. Especially if those screens or components are not in the scope of Selenium locators (e.g. Non-HTML UI, Native Windows, Desktop Apps, SVG components etc.) Integration with Sikuli makes Selenium automation comprehensive. Sikuli complements Selenium capabilities, and integrates with Selenium seamlessly.

We have empowered Selenium to identify non-HTML UI by extending Selenium locators (by.xpath, by.CSS) to identify the components with "by.image."

One of the biggest challenges in the process of software regression test automation is to handle traceability. The main purpose of traceability is to establish bi-directional trace between functional requirements, change requests (enhancements or improvements), bug fixes, and regression tests. Manual maintaining of the traceability matrices can be real nightmare and time consuming.

In this session, I will show you how Selenium-based automation framework can be integrated with Atlassian JIRA to achieve ‘live’ traceability of regression tests to requirements.