News for hackers. Stuff that matters.

A comment on Why Recorded/Playback Tests in Selenium Break.

Re:Why Recorded/Playback Tests in Selenium Break by wildpeaks on Tuesday April 18, 2017 @03:14AM (#14137026)
Personally I prefer Protractor (wrapper for Selenium / WebDriver) to Selenium IDE: despite being officially advertised for Angular, it works just fine for non-Angular as well, and takes care of installing and updating webdrivers, and the tests are code instead of a wysiwyg UI.
[ Parent | on HN ]
Re:Why Recorded/Playback Tests in Selenium Break by Vinnl on Tuesday April 18, 2017 @04:25AM (#14137232)
There's not much sense in using it on non-Angular projects, as all it adds to Webdriver is stuff to work with Angular's digest cycle. Regular Webdriver should work just fine for writing tests in code as well, and you can use webdriver-manager [1] or selenium-standalone [2] to install Selenium and keep the drivers up-to-date.

[1] https://www.npmjs.com/package/webdriver-manager [2] https://www.npmjs.com/package/selenium-standalone

[ Parent | on HN ]