I like the visual method of writing scripts, but having used Selenium + SauceLabs.com on a real app and dealing with functional browser tests every day, I'm concerned about: * Timing issues; most of the time spent writing functional tests is knowing when to wait for the next click (e.g. waiting for AJAX response and change in a certain DOM element)... and doing this in a clean way (e.g. WebDriverWait conditions inste…
> Timing issues; most of the time spent writing functional tests is knowing when to wait for the next click (e.g. waiting for AJAX response and change in a certain DOM element)... and doing this in a clean way (e.g. WebDriverWait conditions instead of putting Sleep(1000) everywhere). This can be answered in a fairly simple way. How does your user know when to proceed? What changes?
They have a 'wait' function that waits for a period of time, but this is just a sign of bad test writing and something sure to break when testing against different browsers or environments (localhost v.s. staging).