1. Selenium tests need to identify the page elements they will interact with by using some kind of selectors
2. XPath seems to be preferred by some because browser tools can get them automatically for you
3. CSS selectors should be used instead, as they are less restrictive and shorter (less code) than XPath. In the workshop practical examples will be demonstrated and can be exercised by the participants, including some selectors that seem impossible to identify

Corina is a senior test automation consultant, with focus on testing by means of Java, Selenium, TestNG, Spring, Maven, and other cool frameworks and tools. Previous endeavours from her 10+ years testing career include working on navigation devices and in the online gaming industry. She loves automation and always tries to learn something new, improving her automation skills and spreading the knowledge to her peers. Apart from work, Corina is a testing blogger (https://imalittletester.com/), a traveler (https://theturquoisecoconut.wordpress.com/), an amateur photographer (https://www.flickr.com/photos/capreoara) and a GitHub contributor (https://github.com/iamalittletester) . She also tweets at @imalittletester.

When writing Selenium tests, you need to identify the page elements by using some kind of selectors. XPATH, although much more complicated than CSS, seems to be preferred by many. Either because testers have tools that automatically extract them, or because they seem to clearly specify the path of the element.
In this workshop i will go over the benefits of using CSS instead of XPATH. I will show a ton of examples, from the easiest and simplest, to the most complex or even impossible. The purpose of the workshop is to get hands-on experience with identifying the CSS selectors for a wide range of cases, which will lead to you dropping XPATH altogether.