Selenium has been around for over 15 years, and by now organizations have realized that Selenium tests need to be treated the same as any other functional code. This means not just keeping your tests in source control, but also designing them to be maintainable and robust. A common design pattern known as the Page Object Model (POM) has emerged, which greatly assists with the organization and maintenance of tests. But there are scalability, speed, and robustness issues with this pattern. This has caused organizations to move away from Selenium for another tooling, however, most organizations are encountering the same problems, because they are using the same problematic design patterns. Max will outline these issues, how to avoid them, and better patterns to use. He’ll discuss how to transform your tests to be more effective, using patterns like Arrange Act Assert, and not relying solely on Selenium to exercise the system.