Timeline for Selenium - Long wait between commands
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 9, 2017 at 17:24 | vote | accept | Sandro | ||
| May 9, 2017 at 17:24 | comment | added | Sandro | Thinking about it, my XPath usually went after CSS properties anyway, namely the class attribute. I haven't started the conversion, yet, but the following seems to be a good resource for such an overhaul. saucelabs.com/resources/articles/selenium-tips-css-selectors Thanks Peter | |
| May 8, 2017 at 14:51 | comment | added | Peter M. - stands for Monica | Implicit is still active, but different parts of selenium command chain (server, grid, webdriver) might have different value than your code has. Using explicit wait, there will be no misunderstandings. XPath is flaky (does not work reliably - see all those questions being asked about XPath not working) and might break after trivial design changes. | |
| May 6, 2017 at 16:30 | comment | added | Sandro | If I don't explicitly set the implicit wait, is it still active? And XPath is somehow buggy? Only for waits? It's my main selection method | |
| May 5, 2017 at 14:51 | history | answered | Peter M. - stands for Monica | CC BY-SA 3.0 |