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 o…
WebDriver Support in Safari 10
11–20 of 37 posts
Re: WebDriver Support in Safari 10
#12This is fantastic news! The blog post doesn't mention iOS. Does anybody here know whether iOS Safari 10 will also support Webdriver?
Re: WebDriver Support in Safari 10
#13Now if we can only get tabs to suspend themselves to free up RAM. Safari is awesome to work with, for the first hour.
Indeed, Safari is the only browser that doesn’t render my machine unusable under such use. (Both Chrome and Firefox seem to consume dramatically more CPU and memory for the same load.)
What kind of situation are you running into where it stops working after an hour?
How much memory do you have on your machine?
Re: WebDriver Support in Safari 10
#14Part of me is thrilled by anything that makes validation easier. Part of me is frightened by the expansion of the attack surface of the browser, particularly given how Apple has been losing their quality edge of late.
I know this is a subjective opinion and I'm not going to touch upon whether I think it's true or not, but I want to know why you even said this bit? The common claims about Apple's quality slipping don't have anything to do with security. If anything, Apple's security is getting better and better over time.
Re: WebDriver Support in Safari 10
#15Now if we can only get tabs to suspend themselves to free up RAM. Safari is awesome to work with, for the first hour.
Re: WebDriver Support in Safari 10
#16Now if we can only get tabs to suspend themselves to free up RAM. Safari is awesome to work with, for the first hour.
(Caveat: I haven't actually tried leaving a Docs page open for a day in a while. I stopped doing that when I discovered how badly it behaved. It's possible Google's fixed it, though I doubt it)
Re: WebDriver Support in Safari 10
#17Now if we can only get tabs to suspend themselves to free up RAM. Safari is awesome to work with, for the first hour.
For me, Safari runs for weeks at a time with several hundred tabs open. Indeed, Safari is the only browser that doesn’t render my machine unusable under such use. (Both Chrome and Firefox seem to consume dramatically more CPU and memory for the same load.) What kind of situation are you running into where it stops working after an hour? How much memory do you have on your machine?
Just keep tabs open, they eventually start chewing up hundreds and hundreds of MB of ram each, and slowly grinds itself into the ground. Relaunch, it's snappy again.
Re: WebDriver Support in Safari 10
#18Now if we can only get tabs to suspend themselves to free up RAM. Safari is awesome to work with, for the first hour.
Are you by any chance leaving Google Docs pages open for a long time? Safari runs great on my machine, with windows and tabs open for weeks at a time, and the only problem I ever have is with Google Docs, because Google Docs is a gigantic memory hog. If I leave a Google Docs page open for a day, it usually ends up consuming several gigabytes of memory all on its own. For a company whose focus is the web, I don't know…
Re: WebDriver Support in Safari 10
#19This 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 o…
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.)