Your current filters are…
by Dan Cuellar
One of the biggest challenges in writing test automation scripts comes in keeping pace with the rapid changes of the application under test. One small “critical” change made by a dev at midnight can result in hours of painful investigation and test script repair for you the next morning(s). However, if you factor your tests properly you can write complex, reliable tests with only a few lines of code that not only test themselves using reflection, but also can be repaired in no time, and repurposed for other platforms. By factoring our selenium tests into scripts(test cases), a model (with hooks to WebElements), and libraries of user actions (e.g. flirt with this user, register, send a message, etc.) Zoosk can quickly write and repair tests for our rapidly-changing and frequently experimental site. The selenium model and library can even be swapped out for libraries that drive other devices (e.g. iPhone/iPad) and use the same scripts to test our mobile apps independently or simulataneously in conjunction with our selenium-automated website / Facebook app.
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.
At Peoplefluent, we have trimmed our test maintenance overhead from ~40% to less than 3% by generating our Selenium Page objects at build-time. We use Java reflection to parse our (constantly changing) presentation layer, and generate these test artifacts, which map to our customer-facing product pages. This moves the conversation to the developer’s desk–when they change something that affects test automation, it either re-generates a new page object unnoticed, or it causes a compile-time failure, preventing them from even checking in code that will cause an automation error. As a side effect, we fully integrated our automation team with the check-ins, build processes, unit testing,and coding standards of the development team. We use the same development languages and tools, and, as a bonus, allowed any developer on the team to write, execute, and troubleshoot functional automation tests from their own workstation. This was accomplished using 100% open-source products (mainly Selenium), requiring only imagination, an investment of time, and a commitment to automating tests at the unit, integration, and functional layers. This presentation will walk through the decisions made leading to this effort, how it was done, and what would be required for any organization to be able to implement the same. We believe this is a completely new way to think about test automation, and it has allowed us to release our software with a degree of confidence we hadn’t known before!
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 Andy Kriger
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.
Welcome Party at The Glasshouse Stores! Appetizers and drinks will be provided. Additional food available for purchase.
16th–18th April 2012