Deep in the implementation of every automated UI test lives the potential to turn something simple into something slow and unreliable—simply by adding extra Selenium commands. The data clearly show that longer tests are less likely to pass. In this case study, I will show you how to optimize a test and make it 560% faster. We will do this by tackling inefficient use of Selenium commands.
As the lead of the Selenium project, I wanted to kick off a new blog series leading up to the release of Selenium 4. During this series, I’ll talk all about how the Selenium project works, who is involved, how you—yes, you!—can get involved, and we’ll get a sneak peek at what’s new in Selenium 4. I've been speaking about this off and on for a while, but now the 4.0 release is looming I wanted to start sharing in more depth.
To kick off Test Automation Day Online | Healthcare, Ryan Vesely, VP of Customer Success and Technical Services at Sauce Labs, provides an introduction to Sauce Labs and our commitment to creating a world of digital confidence (https://saucelabs.com/digital-confidence).
In this session, Sauce Labs Director of Product Marketing Alissa Lydon shares how Sauce Labs is delivering on its 2020 product roadmap and introduces new features including Failure Analysis, Visual End-to-End Testing, and the Sauce Testrunner Toolkit (https://saucelabs.com/platform/sauce-testrunner-toolkit).
