selenium

If using Selenium's Python bindings, you can take a screenshot from Selenium and convert it to OpenCV format like this: cv2.imdecode( numpy.asarray( bytearray(base64.decodestring(driver.get_screenshot_as_base64())), dtype=numpy.uint8), cv2.

In my experience, an exception is thrown in my Selenium test if a button is hidden or not clickable and I try to click it.

Yup, Selenium has been around since 2004, and is now the basis of the W3C standard [1] for browser automation.

Catching all the exceptions thrown by Selenium instead of returning booleans was just an added benefit.

Most Selenium tests don't test that a button is actually clickable though, they find things through the DOM and if the button is offscreen or hidden they won't realise it.

Our platform makes Selenium testing, JavaScript Unit testing, manual testing, and mobile application testing hassle-free.

Once you figure out ways to solve those types of issues, testing things with Selenium becomes a lot more stable and easy.

I'm stuck now with the integration tests failing because they can't run the Selenium Chrome webdriver.

It sucks if you're relying on Selenium testing for verifying your code as you're writing it, but before and after deploys to staging and production?

I was trying to print (shipping labels from Amazon) and Selenium (at least Chrome webdriver) can't see the print dialog:( Any ideas?

For example: Do not write extensive unit-test on the UI but definitely have extensive Selenium tests for the UI _library_ (if you are a library builder).

> It seems that you try to use selenium 2, or webdriver, in order to run your unit tests.

This isn't a sarcasm or criticism but a serious and legitimate "ASK" because I'm working on a large-scale SPA project that's hard to write automation test other than Selenium.

Testing for a page load without JS error is a fine use case, and is an example of what I meant by the "faintest of smoke tests." It's a test that has very little chance to flap, fail, or force you to write hacky commands around Selenium's unreliable API.

> doWithRetry takes a function with no return type > > def clickFillColorWell(implicit user: LucidUser) { > doWithRetry() { > user.clickElementByCss("#fill-colorwell-color-well-wrapper") > } Unlike Selenium, when testing the UI of an external device we have no way of noticing whether an action failed, other than by checking the device's video output.

I ran into a problem with the automation project I was working on when I tried using Selenium.

Nothing too fancy, but just looking at the pure-Selenium coffee examples people have posted here shows how dramatic the effect can be.

I went over those pages briefly and I wish it's not Selenium-like but it kinda is...