[janekk]

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 instead of putting Sleep(1000) everywhere).

* Ability to expand the tests to do other things; for example, Selenium can take screenshots of the browser window because it works at a lower level. We use this for regression testing our web pages.

[IanCal]

> 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?

[janekk]

Ian, I agree that's the right mind frame to be in, but I notice they (DevExpress) didn't address it in their demo or docs.

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).

[IanCal]

Hi, sorry I didn't see this reply before.

Only a wait function would be worrying, it'll lead to unstable tests and more annoyingly tests that don't do what they say. Decent async support is the first thing I look for in testing libs like this.