The problem
I came across this issue the other day and with the help of a friendly developer we narrowed this down to a post-back timeout.
Selenium states “[error] Element 100_page1_Page1Information_button1 not found” when clearly the button is there on the screen.
I can click the button and the test can continue but Selenium barfs due apparently not finding the button.
The reason
The command before this one in the script changes a drop down which then does a post back to refresh a list shown on the same page. The problem is that the Selenium test is moving to the next command (push the button) whilst the post-back is still taking place.
The solution
A simple solution exists – slow the selenium playback script down. Re-run the test and the next step in the script should hopefully occur after the post back has happened.
![clip_image004[3] clip_image004[3]](http://blogs.imeta.co.uk/images/blogs_imeta_co_uk/RLambert/WindowsLiveWriter/Seleniumstatingbuttonnotfoundwhenclearly_984A/clip_image004%5B3%5D_thumb.jpg)