From the course: Robot Framework Test Automation: Level 2

Unlock this course with a free trial

Join today to access over 22,600 courses taught by industry experts.

Real-world troubleshooting example

Real-world troubleshooting example - Selenium Tutorial

From the course: Robot Framework Test Automation: Level 2

Start my 1-month free trial Buy for my team

Real-world troubleshooting example

“

- [Instructor] As you can see by looking at the Selenium2Library documentation. The vast majority of the Selenium2Library keywords all require you to pass in a locator. We see locators here, locators, locators, locator, locator and so on. Along with using static HTML IDs, I'm going to encourage you to use XPath and CSS as much as you can. Instead of those lighter weight, easier Robot Framework options. And I only say that because it makes your scripts less ambiguous and gives you confidence that you're interacting with the exact element that you want to interact with. So if you're new to test automation, XPath and CSS might seem a little bit intimidating. But fortunately the FirePath tool will produce usable locators probably 80% of the time, and as you slowly learn more about XPath and CSS. You can even optimize the suggestions that FirePath gives you or choose alternatives that work better with all browsers. Speaking of working with all browsers, make sure that when you do use the…

Contents