Your current filters are…
The web is accessible anywhere; from the phone in your pocket to tablets, TVs and cars. As web developers we have a responsibility to ensure that the web stays open and accessible to everyone, regardless the kind of device being used. In developing countries mobile phone telenetworks are often built before traditional landlines offering broadband access, and ensuring that web sites work well on low-end mobile phones is an important social factor for spreading knowledge and bridging the world. Since the introduction of OperaDriver one year ago at this conference, it has taken many leaps forward in becoming device and product agnostic. The talk will demo and introduce Selenium support for all Opera devices, including baked-in support for a range of mobile emulators. Join this talk and learn how to bring the internet and testing to any device, anywhere.
Robust test automation frameworks are not designed and developed upfront, they are evolved over time. I have found it useful to have vision for a robust, scalable and reliable framework – but focus should be on solving the current problem. In this talk, I will demonstrate how we can start with simple, fragile test scripts and continuously re-factor them to build a robust framework. In every stage of re-factoring (or design improvement cycle), I will discuss – What are the limitations of current state of automation code / framework? – What design improvements might overcome those limitations? – How best they can be implemented with web driver? – Implement and repeat cycle. Talk will begin with a recorded / exported script and will evolve in a decent framework by implementing page objects, components, workflow, domain objects, asserters and so on.
by Jim Evans
As new browsers start to appear (Silk, headless browsers, and so on), there are opportunities for creating new drivers. What are the best methods to use if you want to create your own driver? In this presentation, we will disect the Internet Explorer driver; examine the decisions made for its architecture, code structure, and technology choices; and use it to extrapolate the methods best suited to building a new browser driver from the ground up.
A detailed guide to creating a mature and paralellizable automated test suite. This talk will cover things such as data independence, atomic tests, state generation, testing oriented pages, and will include sample code, demos, and funny cat memes.
by Mike Davis
I am TL for a small team at Google. My team work with various product teams to help them release better software, faster. Helping teams to write useful integration tests is one great way to help them improve their development cycle. In this talk I will outline: How selenium & integration testing fits into our development cycle. Making web tests reliable, fast, easy to write, easy to read & easy to debug. How we get developers to write & maintain selenium tests.
by Luke Daley
Geb – http://gebish.org – is a browser automation solution for Groovy. It brings together the power of WebDriver, the elegance of jQuery content selection, the robustness of Page Object modelling and the expressiveness of the Groovy language. Geb enables more expressive, more concise, and (very importantly) more maintainable web tests.
Mobile testing is different than desktop web testing. It needs the right tool for the job. In this case, we need robots. Lots of them. Lots of little robot fingers touching lots of little mobile device screens. In this talk, Jason Huggins will bring out some robots from his lab and demonstrate how you, too, can join in the robot revolution that will destroy civilization… and make a decent living testing mobile apps in the process.
Unstable back-end systems ? Changing data ? Test and production two worlds apart ? Based on real project experiences, this talk is about Selenium-based approaches to how quality can be achieved against all odds. With code.
by Michael Klepikov
by David Tolley and Jesse Dowdle
Most engineering organizations include some level of continuous integration in their development process. The brutal truth is that far too often these efforts are plagued by unreliable tests, long feedback loops, and bad configuration management. Learn how AtTask decided to radically rethink their software development model, and by using open source and cloud solutions went from 3 days of acceptance testing to just minutes, providing feedback on thousands of selenium tests to every engineer in the organization. See how by leveraging publicly available tools, you can deliver hyper-scalability to your Continuous Integration framework and include selenium testing per commit to drive cycle time down in your organization.
by Liz Keogh
When we test code and find it doesn’t do what we thought it did, we change it. But wouldn’t it be great if we didn’t have to write the wrong code in the first place? In this talk Liz shows how we can use examples and scenarios to break the models we make inside our own heads, helping us to avoid premature commitments and their follow-through – whether in code or in life.
This State of the Union address will cover what’s been done in the year since the last SeConf, point out some of the highlights and lowlights, and then roll forward to look at our future plans. By the
end of the talk, you should have a good understanding of where the project is, where it’s going, and why it’s going there.
Selenium Builder is a new Firefox plug-in for working with both Selenium 1 and 2. It has a clean and simple user interface for recording, playing back and editing scripts that allows you to seamlessly work with both versions of Selenium. Builder’s user interface is built on HTML and JQuery and is designed to be a lot cleaner and more streamlined compared to Selenium IDE. While not as fully featured as IDE (yet) it allows you to quickly record new scripts, edit steps, and try out scripts in-browser. Builder also currently supports exporting Selenium 2 tests to Java and Python and introduces a JSON-based format for storing tests to be opened and edited again later. Selenium Builder is still in beta, so your input and skill along with your suggestions are very much appreciated. Builder already supports Selenium extensions, and we want to develop a complete plugin system so that extra features such as Flash support can be added. We’re looking to find out from you: What would SB need to be integrated properly into the way you use Selenium right now? What would make you switch from Selenium IDE? How can Builder help you migrate to Selenium 2?
by Noah Sussman
In 2006 a friend turned me on to a new test harness called Selenium. The framework had little documentation and ran inside a weird, janky frameset. But Selenium had two killer features: you didn’t need Windows administrator privileges to install it and it was the only free GUI-driven regression testing framework for Web sites. Five years later I find myself in the position of having used Selenium in a business context for almost half my career and nearly the entire lifetime of the tool. Selenium’s changed a lot, so have the Web sites it was designed to test, and so has the Web itself. I look forward to talking about how I have helped businesses leverage Selenium to manage change and increase their ability to adapt in the ever-evolving world of eCommerce.
At Groupon we utilize a ‘Pluggable Test Infrastructure’, where we express tests using high-level behaviors, and avoid precise web actions like “click”. We build tests around behaviors and outcomes. The infrastructure “plugs in” multiple test implementations at runtime for multiple uses of the product, like web, mobile, API, and International. Given a logged in Groupon user When I choose to buy a deal Then I should be informed that my purchase was successful That test can be exercised on the website, an iPhone, and via the Groupon API. Instead of having three separate tests, we have one that describes our behavior, and three automated flows to drive it. For web, mobile, and international web, we utilize Selenium/Web-driver. For the API, we exercise the same behaviors on the back-end via curl. All of these are driven by the same high-level, natural language specifications. One test, multiple implementations. Our presentation will detail this strategy, the benefits (product quality + developer feedback), and the occasions to use it (and not use it).
In this talk we will discuss how to use PhantomJS as a backend for RemoteWebDriver. The main purpose is to speed up the execution of test scripts, getting rid of the _bloated heaviness_ of real web browsers, and substitute them with this lightweight headless browser that everyone is talking about.
I’ll present a summary of my recent experiences building a suite of automated tests for my client’s native iOS application. I’ll cover both the technical aspects, (including an overview of the toolchain, and issues I had setting up a continuous integration build), as well as the cultural ones (such as the challenges encountered when attempting to incorporate test automation into a development culture that traditionally has not included it.)
by Matt Wynne
Tools like Selenium make writing automated browser tests dead easy. Many teams never look further than this, and are satisfied with just replacing their laborious manual testing efforts with reliable Selenium scripts. They’ve missed a big opportunity. If your test scripts talk in terms of button clicks and form interactions, they are hiding what’s interesting about your tests – the language of your domain. These tests are also brittle, breaking easily as the site’s design evolves. In this entertaining talk Matt will show some very bad examples of browser automation scripts, and explain how using a higher level of abstraction – writing in the language of your domain – will create more happiness on your team.
Security Testing is often seen as a specialist skill or role, but there is a range of static and dynamic security analysis tools that can be used by testers to perform common security checks. Unfortunately the dynamic security analysis tools require manual exploratory testing and are not compatible with continuous integration. This presentation will show how the Zed Attack Proxy (ZAP) can be combined with browser automation tests to provide fast automated feedback on common security issues within web applications. The talk will take attendees through adapting existing Selenium based test suites, an overview of performing automated security analysis with ZAP, and incorporating this into Continuous Integration for fast identification of security issues as they are created.
16th–18th April 2012