selenium

Selenium has a pretty good Bazel setup which uses a lot of different functionality: https://github.com/SeleniumHQ/selenium/

* Home Automation, like opening shutters at sunrise and closing them at sunset or turning on LED lights at night when movement is detected and turning them off after a certain amount of time since the last movement. Z-wave relay modules control most devices, and the command-center is Raspberry Pi + Aeon Z-Stick (aeotec.com/z-wave-usb-stick/), which allows for a vast amount of flexibility compared to standard Z-Wave controllers. * an extensive collection of custom made /usr/local/bin scripts which automate things such as video recording and encoding for youtube (recordmydesktop + avconv), backups, and certain time-taking and repetitive operations on websites (like downloading invoices; through selenium-webdriver - github.com/SeleniumHQ/selenium/wiki/Ruby-Bindings) * zaps on zapier.com for pushing data between multiple cloud services that w

Also look at stuff like this... https://github.com/SeleniumHQ/selenium/pull/5468

I agree that implicit wait is something of a time waster. Regarding clear, that does appear to be exactly what the Python implementation does[0], but in my experience it just seemed to fail at random. If I remember correctly it worked most of the time with geckodriver, and then hardly ever with chromedriver. Really not sure what exactly the deal is with that... And yes the time wait is a little pointless (: [0] https://github.com/SeleniumHQ/selenium/blob/master/py/seleni...

I agree that is is important to structure the application to facilitate testing. But I find this surprising: > And while recorders present some challenges, manually coding UI-level tests make the maintainability issue an order of magnitude worse. In my experience, writing the tests manually for sufficiently "regular" applications ends up being more maitainable because you can put repeated logic in shared functions and classes, making it easier to adapt to changes in the GUI. Page Objects are an example of that: https://github.com/SeleniumHQ/selenium/wiki/PageObjects Also, writing the tests manually lets you use "explicit waits". http://elementalselenium.com/tips/47-waiting Specifying exactly what we expect to happen tends to be more robust (and faster) than either using static sleeps or some kind of implicit wait. Recorders tend to have p

That proxy already exists. It is called ChromeDriver[1][2] and was developed in collaboration between the Chromium and Selenium teams. It is the same way that Selenium/Webdriver controls regular Chrome now. It would have been nice if they at least mentioned it in the article since Selenium is such a popular browser automation tool. They do in fact mention it on the README page for headless chromium. [1] https://github.com/SeleniumHQ/selenium/wiki/ChromeDriver [2] https://sites.google.com/a/chromium.org/chromedriver/home [3] https://chromium.googlesource.com/chromium/src/+/lkgr/headle...

selenium has moveto[1] which will move the mouse to an element. you would use it in an action chain. [1] https://github.com/SeleniumHQ/selenium/wiki/JsonWireProtocol...

"Showing 930 changed files with 13,029 additions and 10,187 deletions. " Feel free to try: https://github.com/SeleniumHQ/selenium/compare/selenium-2.47... It's a dependency of a dependency with multiple language versions in the one repository.