The web ecosystem has changed a lot over the last decade. From displaying static generated HTML code to running complex web applications, the browser has become the software of choice to provide great user experiences across many platforms. With new powerful features like WebXR or WebAssembly, more and more capabilities are being shipped to the browser every year allowing it to provide an even more enriched experience on the web.
With every novel API available in the browser, new interactions between the user and your application are possible, which increases the complexity of your frontend application and the area for bugs being introduced. At the same time we are putting more load on the browsers main thread while trying to manage a fast page load and smooth animations. The web is moving fast, however browser testing appears to still be the same. A lot has changed in recent years, new JavaScript automation frameworks have been popping up that addresses a lot of pain points that developers face. The MDN Web Developer Needs Assessment has shown that providing a consistent experience across browsers, even on outdated ones, is still a high priority for developers today and becomes even more important tomorrow. But how are the browser automation frameworks tackling this challenge to allow their users to test their applications using all these new upcoming browser features?
In this session, we’ll take a look at what has happened behind the scenes in browser automation throughout the years and what the future will have in stock for us. We will examine how web testing will develop and what challenges this will bring for conventional frameworks like Selenium or WebdriverIO, as well as new frameworks such as Cypress, Puppeteer and Playwright. Lastly, we will experiment with some new automation capabilities these frameworks provide to test some of the new web features.