Do you find it confusing when your Selenium test sometimes waits for a page to load and sometimes it doesn't? Do you get frustrated that you can't check to see if an alert is present on the page without canceling it? Are you constantly sending timeout commands during your tests? There are several ways you can customize the behavior of the browser you are using to test when you start a session. You can leverage these settings to ensure consistent and reliable behavior across different parts of your tests to minimize time spent investigating failures. The W3C specification for WebDriver has also added several helpful options that are still underused. Additionally, each browser vendor offers custom ways for working with their browser.

In this webinar, Titus Fortner, Senior Developer Experience Engineer at Sauce Labs, will walk through how WebDriver capabilities work and will provide examples and demonstrations of the behavior in action. At the end of this session you’ll understand how to set and work with:

• Timeout values
• Page loading strategy
• JavaScript alerts
• Insecure Certificates
• File Interactability
• Plus various vendor-specific preferences and extensions
Tue, Jun 29, 2021 · 2:00 PM Eastern Time (US & Canada) (GMT -4:00)
Titus Fortner
Senior Developer Experience Engineer
Titus Fortner is a core contributor to the Selenium project and the maintainer of the Ruby bindings. He spends a significant amount of time writing open source testing software built on top of Selenium. He is the project lead for Watir and is active in supporting these projects on Stack Overflow, message boards and in the Selenium Slack and irc. Titus has implemented automated tests at five different companies and currently works at Sauce Labs as a Solution Architect, working with the community to facilitate testing best practices.