Having an issue with the old "element not found in cache."
Googling it, I came up with:
http://code.google.com/p/selenium/issues/detail?id=1887
Comment 3 by leo.lath...@gmail.com, Jun 25, 2011
This happens for me a lot. I suppose that my page is too dynamic and it invalidates the references too often.
So I had to add a catch for the StaleElementReferenceException and retry the instruction for every selenium find. For me, that doesn't make much sense.
If the cached element is stale, shouldn't the cache miss trigger a new request to refresh the element?
Comment 4 by savag...@mail.ru, Jun 26, 2011
Thanks for your advice. I added a catch and everything works, but... it looks like a workaround or something like that. I thought it should work automatically.
http://www.echographia.com/blog/2011/01/13/element-not-found-in-the-cache/
No comments:
Post a Comment