3 ms·
I went with CodeceptJS [1] instead (Seleniu in nodejs, with most of the async madness abstracted away) for the last project, but, as thangalin says it best "It
by nnq 10y ago
I went with CodeceptJS [1] instead (Seleniu in nodejs, with most of the async madness abstracted away) for the last project, but, as thangalin says it best "It is a lot of effort to automate user interface testing with Selenium, especially for web applications with complex user interfaces, concealed options, and so forth.".
Advantage is that testrunner code mingles seamlessly with injected-into-browser-js. Problem is... complexity, and twilight-zone-class bugs in the testing tools themselves: there comes a point where the logic of the acceptance tests is so convoluted, and they are so undebuggable and unmaintainable, that fixing and extending them eats the time of the best and most expensive developers, instead of being a great tasks for juniors...
Eager to try helium next, hope it sucks less :)
[1]: http://codecept.io/ http://codecept.io/
Edit+: don't get me wrong, CodeceptJS is amazing compared to the madness of seleniu-webdriver/webdriver.io used "raw", with promises and callbacks, so kudos to its devs. But its far from optimal... though this maybe because selenium itself is far from optimal.