3 Answers
3

thanks.. that's good to know... +1 ... I was testing with this wait when I had the linkText, so I'll correct that (good catch) ==> driver.Manage().Timeouts().ImplicitlyWait(TimeSpan.FromSeconds(10)); ... my actual issue seems to be related to this waiting
–
MacGyverJan 17 '12 at 20:18

+1 for you my friend.. however I found the issue. Perhaps you can help me find a better alternative to my solution. It was related to the waiting.
–
MacGyverJan 17 '12 at 20:20

1

Personally, I don't even like Selenium's wait functions, they seem too fragile and I have to be explicit in what I want to wait for. In my selenium wrapper classes I implemented polling/retry logic on every action, so I can navigate to a new page and immediately call a click method on an element I know won't appear for another 10 seconds and it will try and retry up to a specified amount of time and eventually either work or time out. This has avoided so many headaches for me.
–
Sam WoodsJan 18 '12 at 22:35

Seems like I have to use this line of code before I invoke any click events. The "clickAndWait" conversion of the Selenium IDE to Webdriver doesn't seem to work properly. It converts everything to *.Click(). Adding the implicit wait after every click event and setting WAIT_TIME to 3 in my Constants class seems to do the trick.