[koollx]

Screenster support for timeouts is much more extensive. It automatically determines the time it takes for the server to process each user action, it uses the visual baseline to wait for the right state instead of timing out or waiting too long.

Obviously you can do everything with WebDriver, Screenster uses it too. The point is that you can get a lot of benefits out of the box when you are using a highler level platform like Screenster vs hand coding to a low level API like WebDriver.

There's some description of Screenster features here http://screenster.io/selenium-alternatives-for-testing-autom...