There has been a recent explosion in second-screen technologies such as Chromecast, but designing test automation for second-screen applications is far from straightforward. This new paradigm lacks major automated tool support, and coordinating test execution across multiple devices is tricky and error-prone.

Our automation solution uses WebdriverJS and WebSockets to perform end-to-end test automation that covers our web player controller and second screen application.

Learn about our approach to second-screen automation which we’ve used to build a reactive, responsive test suite. We’ll describe our solutions to synchronizing test flow between the controller and target device, validation on the device, targeting different integration components, and device management.

Selenium is mostly used to test JavaScript/HTML applications.  However, several organizations use Java WebDriver bindings to develop their automation.  Our team has learned that WebDriverJS provides a number of benefits over the traditional approach.  Asynchronous constructs in Javascript, such as Promises and Reactive-Extensions (RxJs), help solve many of the challenges faced when developing automated tests for browser based applications. With the increase in popularity of Node.js, JavaScript is being utilized across the entire web development stack.  WebDriverJS complements this trend, by enabling functional tests to be written in the same language as unit tests and production code.

Learn how your team can benefit from the adoption of WebDriverJS and complimentary JavaScript tools and libraries.  We will discuss our motivations, as well as the architectural and design decisions that applied to our use case.  The presentation will conclude with a real-world demo of using WebDriverJS and RxJs to implement the Page Object Model.