Live data from Hacker News

Announcing Browserling: Interactive cross-browser testing in your browser

catonmat.net

41–50 of 56 posts

Re: Announcing Browserling: Interactive cross-browser testing in your browser

#42
I was using http://spoon.net for a while. As far as I can tell they are basically a further developed version of this.

Unforutantely it looks as though Microsoft was none-too-pleased with their inclusion of Internet Explorer as one of the virtualized browsers and has forced them to shut it down. Hopefully you can elude the same fate...

Also, while I'm typically ok with the cartoonish trend of most startups these days, I'd have to say browserling might have gone a bit overboard with the whole thing. I know your only in beta and I'd have to assume things will change as you continue to develop.

Best of luck to you guys!

Re: Announcing Browserling: Interactive cross-browser testing in your browser

#43
This could be super helpful. I don't think anyone here doesn't feel the pain of cross browser testing.

I think that the queue is an interesting concept. I understand that you have to tier your system, but it made me bounce, and not want to go back. If you keep it, find a way to make it clear and seamless.

Re: Announcing Browserling: Interactive cross-browser testing in your browser

#44

Tried it out for IE6 and when the window loaded, someone else's site was up and I was unable to do anything while the counter ticked down. A bit concerning from a privacy standpoint. Maybe the machine fell over?

I had about the same; when switching to Firefox, it opened a new tab and before this was opened I was still able to look at an existing tab of someone else.

Re: Announcing Browserling: Interactive cross-browser testing in your browser

#45
post #38

I just tried this, but didn't even get to use it. I entered the URL for a site I'm building, wanting to see if IE9 was going to screw me up (I'm still on WinXP), and I was sent to a queue. My only real complaint about the queue is that you give absolutely no indication of how long the expected wait time will be. This would be reasonable, except for the countdown clock, which simply read 00:00 the whole time I was wai…

I ended up on a "Loading" page during the whole 90 seconds and then was told that my time up.

Sorry about that! When the API servers go down (these interface with our windows servers) it tells everybody in the queue "time's up" instead of a more informative message since we're using connection drops as a poor way of passing along the session expiry event.
Post reply on HN