Selenium Conf Day 1

Fri, Sep 5
08:30

    Registration - 30 mins

10:15

    Coffee/Tea Break - 15 mins

10:30
  • Added to My Schedule
    keyboard_arrow_down
    Jim Evans

    Embrace and Extend: How the Selenium Project Convinced the World's Largest Closed-Source Company to Participate

    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.

  • Added to My Schedule
    keyboard_arrow_down
    derrick

    Design Patterns beyond the Page Object: An investigation into the design patterns used while building page objects.

    In an age where the Page Object Pattern and Page Factory Pattern dominate web testing conversations, there is still a need to understand and apply the design patterns of yesteryear. Ideas from the Facade Pattern, Factory Method Pattern, the Iterator Pattern, the Object Pool Pattern, and the Decorator Pattern all find their way into the Page Objects we build to represent the increasingly complex widgets found on today's websites.

    In this presentation, we take it back to the old school, looking at novel ways to apply classic design patterns, like those developed by the Gang of Four and Code Complete, to new screen scraping problems. We will investigate three common scenarios where using the typical approach to page objects can be inefficient or difficult, including filling in a web form, iterating over data in a list, and traversing iframes to communicate with widgets. We will explore how to improve upon the naive approach to building these page objects through the use of classic design patterns. Finally, we will formalize our findings into new patterns which can be applied to more general scenarios.

    Code examples will be presented in Python and based off of my work building automation tools for hubzero.org, a platform for scientific collaboration.

  • Added to My Schedule
    keyboard_arrow_down
    Yagnesh Shah

    Designing selenium webdriver scripts in an effective manner to reduce script rework and Reporting Dashboard

    Automating a test scenario can be pretty easy once we get a hold of any tool. Designing hundreds of tests and making sure that the script rework involved for each release is at minimum, takes a good level of experience. Collection of such good practices & the architecture for designing all your test scripts will be demonstrated.

    To enable you start with selenium webdriver for your own project. Template which will quickly facilitate you to initiate scripting with some of our additional user defined libraries. Example, read/write to excel sheet and many other. Hands on practice for scripting test scenarios as per the automation architecture to ensure less maintenance of scripts.

    We will also demonstrate how to handle reporting for hundreds of tests on real time basis for each test suite and hence making our stakeholders aware of the test results on real-time. Our code for this reporting dashboard will be available for the testing community on github.

11:45
12:30

    Lunch Break - 60 mins

01:30
02:30
03:00

    Coffee/Tea Break - 15 mins

03:15
  • Added to My Schedule
    keyboard_arrow_down
    Dhimil Gosalia

    Running Selenium tests on a cloud of real mobile devices

    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.

     

  • Added to My Schedule
    keyboard_arrow_down
    Prasanna Kanagasabai

    Testing "Injection" Attacks with Selenium

    Business applications are growing at a break neck speed to cater to ever increasing business need. The dream of ever-connected systems and information at fingertips is quickly becoming a fact. This dream has brought out an evolution of online-real time applications with multiple requirements and functionalities. The down side to this security is being forced to take a back seat. Add to this the sheer quantum of code to cover is overwhelming to a manual security tester.

    One of the most common attacks against web applications is injection attack; injection flaw allows a malicious user to send malicious input to an application. The consequences of having injection flaw in your application can range from a user be able to steal all the data from your database to extreme situation like he having a command access to your infrastructure. We in this session want to show the power of automation using selenium. We will demonstrate how we are writing some interesting scripts to automate the testing of injection attacks in web applications. The outcome of automation is that we have been able get a fair code coverage and gives the time to security tester to concentrate on more tests that need his manual expertise say business logic failure or a design failure. 

    Though selenium could be used to automate far larger scope but we choose Injections as a priority for these sessions as injections form a large part of the web application attack landscape. We intend to give you some of the learning’s we had in the past, and some pitfalls we noticed. One could take the same idea and extrapolate to other attacks too.

    Attacks we plan to cover 

    1. SQL Injection 

    2. Command Injection 

    3. XSS 

  • Added to My Schedule
    keyboard_arrow_down

    Lightning Talks

04:30
07:00

    Sauce Labs Reception (with Dinner) - 180 mins

Selenium Conf Day 2

Sat, Sep 6
10:15

    Coffee/Tea Break - 15 mins

10:30
11:45
12:30

    Lunch Break - 60 mins

01:30
02:30
03:00

    Coffee/Tea Break - 15 mins

03:15
05:00

    Closing Talk - 30 mins