4 ms·
> I don't understand the requirement for adding new browsers 'instantly and on-demand'. Because the major JavaScript libraries' timetables should not be bound
by jeresig 18y ago
> I don't understand the requirement for adding new browsers 'instantly and on-demand'.
Because the major JavaScript libraries' timetables should not be bound by how willing they are to twiddle config files/write new browser loaders in Java. It shouldn't be anymore complicated than hitting a button that says "Add this browser as a new test base."
> I'd be curious to hear those arguments and to have examples of when virtualization is not sufficient and you need to go to the actual user's machine.
Timing, performance analysis, and CPU/memory availability are huge ones. Being resource constrained in a VM is not an acceptable approximation of what a user's desktop actually is. Nor is running a mobile browser in a simulator. Nothing beats running an actual browser on an actual desktop.
If you were to argue that you could have no resource constraints in your VM, that brings it back to the argument of cost and resources.
- jgrahamc 18y ago> Timing, performance analysis, and CPU/memory availability are huge ones. Being resource constrained in a VM is not an acceptable approximation of what a user's desktop actually is. Fair enough. Don't you run into the same problem with volunteer machines though? You can't actually control their configuration in TestSwarm so you can't control the resources (e.g. you can't control what else the machine is doing). If you are going to do do any serious analysis of timing or performance then you are going to have to control the machines.
- jeresig 18y ago> If you are going to do do any serious analysis of timing or performance then you are going to have to control the machines. Absolutely - the timing and performance won't be more accurate but it will be more realistic. For accuracy everything has to be done on the same machine in a 'clean' environment (and definitely not in a VM).