Hacker News Reader

Comment by maspwr | Hacker News Reader

This looks really great. Baking in support for test automation seems like a no-brainer and a welcome step forward for web development.

Are any other major browsers taking a similar approach to Safari in terms of native WebDriver support? I saw this Microsoft blog [1] on Edge support of WebDriver, but it's not clear to me what approach they have taken (you still need to download a separate server for instance).

Only one Safari browser instance can be running at any given time, and only one WebDriver session can be attached to the browser instance at a time.

One downside to this approach is that it limits the ability to parallelize tests on a single machine for efficiency purposes.

1. https://blogs.windows.com/msedgedev/2015/07/23/bringing-auto...

View on HN

"Are there any other major browsers taking a similar approach to Safari in terms of native WebDriver support?"

Let me tell you about the "world domination plan" for the Selenium project. In the beginning of the project, no browser had a good automation story. It was a constant battle to catch-up and fix things every time a new browser version came out. With Selenium 2, in addition to merging in WebDriver, the grand strategy was to move the maintenance of each browser driver codebase to the browser vendors themselves. Opera, Mozilla, and Google quickly jumped on board with the idea. To further this strategy, we moved Selenium's IP to a neutral 3rd party (Software Freedom Conservancy), and worked towards a W3C browser automation spec that looks suspiciously identical to the WebDriver API. Now with Microsoft and Apple also on-board, we can all raise our glasses and yell "Cheers!"

Of course, there's no rest for the weary. The battleground for good test automation tooling has now shifted from desktop to mobile (and possibly TVs, cars, watches, IoT, etc.)

I wonder... Boss - "I see you expensed a Tesla" Me - "Yes, its for browser testing..."

You kid, but at some point over the years, I had that same epiphany: If you want a built-in justification to play with any new toy, pursue a career in test automation! (I don't have a Tesla, yet, but I'd be happy to be invited over to the test track to talk shop... But seriously folks... I'm very curious how they test the software running on their dashboard and center console.)

Google's advice was always emulation--the tests running on dozens of Dell servers were faster and more reliable at bug hunting than physical hardware. Obviously there are limits, but the advice in 2013 was to prioritise automated tests in simulators instead of on real devices. Note the emphasis on automation, though -- you can totally expense that Tesla for the manual/acceptance testing ;-)

Emulation, and specifically domain modeling, goes a wicked long way and has huge speed advantages in general.

"But couldn't you run it in a VM?" ;-)

Then again, I can't actually find a VM for QtCarBrowser... short of downloading an old version of QtWeb presumably...

This is why there's a market for robots for testing -- real robots hitting real buttons. Especially in the automobile industry, no company wants to be hauled in front of the oversight committee in Congress after some horrible accident and when asked how they tested everything, they're only able to say "Well, all the tests passed in the simulator, so we went straight to production..."

Both Chrome and Firefox already support WebDriver. They both allow tests to run in parallel by opening multiple windows.

Does that limit multiple tabs/windows? I would assume that a browser instance is a collection of multiple window contexts.

Reply on news.ycombinator.com