[sho]

Not sure if you are being sarcastic, but if testing on your browser means downloading a 4GB+ image every couple months and having it take up all my memory in a clunky VM and messing around with how it gets its IP and then trying to update itself with another multi-gigabyte windows update while I'm tethering and did I mention you have to redo it all every couple of months?... then I'm not testing against your browser.

[millstone]

Then how are you testing your browser? Are you assuming that testing Chrome on ThisOS is sufficient testing for Chrome on EveryOtherOS?

[UweSchmidt]

One thing is testing if the fancy custom react component works properly in a particular browser at all, that should be the case in a certain browser+version across OSes and you'd want that available all the time.

The other thing is testing if some CSS is acting up in a specific Browser/Browserversion/OS/Screensize/Phone combination; that is probably a job for QA.

[jodrellblank]

There's a startup for that: https://www.browserling.com/ run by user pkrumins

https://www.browserling.com/browse/win/7/ie/11/https%3A%2F%2...

[UweSchmidt]

There is also http://saucelabs.com/ and https://www.browserstack.com/ who have real devices and allow you to run automated tests.

[alexmcpeak]

As well as https://crossbrowsertesting.com

[mschuster91]

> and messing around with how it gets its IP

Standard VirtualBox is either bridged or NAT, never had a problem there.

> and then trying to update itself with another multi-gigabyte windows update

Now THAT one is a real problem. MS to this day didn't bother to release a Service Pack 2 for W7.