Selenium scripts not working in Selenium 3 grid once the application Angular version is upgraded to 17

[Snehal Wale Bhosle]

Hi All,

I have been facing this issue a very long time now and not able to find any solution. Our automation scripts have started failing due to below reason on Selenium 3 chrome node after angular is upgraded to Angular 17.

- Exception occurred at =: element not interactable

- Exception occurred at =: no such element: Unable to locate element

-Exception occurred at =: element click intercepted: Element

Can some one please point out what could be the solution to this issue. We have tried below solutions, but nothing has worked till now:

1) Selenium grid upgrade to Selenium 4: scripts are failing as the Selenium grid 4 is not stable

2) Added waits for element presence

3) Tried clicking elements using Action classes

4) Used JAvaScriptExecutor

Thanks,

Snehal

[Techical Kunal]

- Exception occurred at =: element not interactable - give more wait or try with thread.sleep and check response

- Exception occurred at =: no such element: Unable to locate element - waits problem, try with thread.sleep

-Exception occurred at =: element click intercepted: check after performing operation some disabled part is getting enable, so it required refreshing page or not

overall - waits problem i can see, try with thread.sleep with max wait if element is taking 5 sec then give 10 sec and check whether it is working or not

--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/c3079cc7-ace8-4731-b178-1d269c314ca1n%40googlegroups.com.