Timeline for How to analyse 'Element not Found' exceptions when working with Selenium
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 17, 2019 at 8:36 | comment | added | PDHide | @NielsvanReijmersdal This can save time to avoid visual inspection manually | |
| Dec 16, 2019 at 18:33 | comment | added | André Roggeri Campos | Sure, there are cases where the element is visible on the screen but the test failed to find it (Locator changed, wrong wait condition, etc). But in my context it helps to find the problem most of the times (The test went to the another page, or there is something on top of the element that I want to click). | |
| Dec 16, 2019 at 15:45 | comment | added | Niels van Reijmersdal | I think this is a good practise for test automation, but I am not sure it helps analysing NoSuchElementException 's. Maybe the screenshot shows the element, now what? Screenshots are taken after the fail, this is atleast some milleseconds, so the element could be drawn afterwards. | |
| Dec 13, 2019 at 1:23 | history | answered | André Roggeri Campos | CC BY-SA 4.0 |