Live data from Hacker News

How to make Selenium tests reliable, scalable, and maintainable

lucidchart.com

1–10 of 71 posts

Re: How to make Selenium tests reliable, scalable, and maintainable

#4
The most annoying thing I found with Selenium was that it wouldn't wait for the browser to respond to click events and rerender.

The approach in the blog post (and I think elsewhere ... not sure) is to poll the DOM with a timeout.

Is there a better solution to be add with something like `executeScript`? You could run `requestAnimationFrame`, and then poll for an indicator that the click, etc. handler has indeed finished. That way if it fails, you know about it pretty soon, without the need for long timeouts. This is all just a guess though.

Re: How to make Selenium tests reliable, scalable, and maintainable

#5
Nice rundown, wish I had read this a year ago!

> One developer designed a way to take a screenshot of our main drawing canvas and store it in Amazon’s S3 service. This was then integrated with a screenshot comparison tool to do image comparison tests.

I would also take a look at Applitools https://applitools.com/ — they have Selenium webdriver-compatible libraries that do this screenshot taking/upload and offer a nice interface for comparing screenshot differences (and for adding ignore areas). Way fewer false failures than typical pdiff/imagemagick comparisons.

Re: How to make Selenium tests reliable, scalable, and maintainable

#8

BrowserMob, that was a sweet service (based on selenium). Does anyone know what happened to those guys after they sold? I've always wanted to learn more about their story.

I don't know about the entire team, but Patrick and Ivan were at Neustar for a while. They're both at NewRelic right now.
Post reply on HN