One of the biggest reasons UI tests break often is the use of unstable element locators. In this session, I’ll discuss strategies to write more stable element locators, introduce UI-licious - a low-code testing tool - and do exercises to show you how to write stable semantic tests with UI-licious to test user journeys, not HTML. Outline What makes automated UI tests flaky? Strategies for writing more stable element locators What is UI-licious? : Test user journeys, not HTML Philosophy Hello world with UI-licious: We’ll do a short exercise to login to GitHub and cover the basic commands to navigate, fill input fields, What about icon buttons and images? : We’ll do a short exercise to test icon buttons and images and explain how UI-licious works to target elements based on accessibility attributes. What about similar elements? Hinting using I.see: We’ll do a short exercise to explore using the I.see command to hint at the element targeting algorithm. Scoping using UI.context: We’ll do a short exercise to use UI.context to set the search scope for the element targeting algorithm. Using Page Object Model in UI-licious: Page Object Model is a good way to manage the complexity of the codebase for a UI test project by creating reusable functions that represent the state and possible interactions with a UI component. We’ll do a short exercise to create a page object model to test a larger website. Fun and Games: Testing 1 to 100 game with UI-licious: We’ll do a short exercise to write an automation script to play a game of clicking numbers randomly positioned in a grid from 1 to 100. Q&A: Open to any questions from the audience.