[ QUOTE ]
My automation suite starts a VM, installs the latest build of the software, verifies it, imports my standard suite of data and takes the software through an entire suite of testcases (presuming they all pass). If something doesn't pass, the automation leaves the VM running, so the bug report and VM are ready for inspection when I arrive to work in the morning.
[/ QUOTE ]
Does anyone else use it this way? I'm headed there. I have my work cut out for me with reading and experimenting.
I'm wondering what VIX API you used (C, Perl, or COM) and why. Any other info, especially examples [img]/images/graemlins/wink.gif[/img], would be greatly appreciated.
PS If anyone knows who/how/what to do to get a new "topic"....I think this example exemplifies how valid a topic "Virtual Machines" would be.
I agree, there is a definite need for a Virtualization section.
I have used VMWare in the past, but only under a single platform (Windows) with different system configurations.
It really does make a world of difference (time wise) when combined with an automation suite. However, if you're performing cross-platform validation then I would suggest a cycle of manual testing against each individual platform, on a middle-of-the-road type system before setting up full virtualization for the platform. This is only because I had run into problems with cross-platform testing in the past and I've been too scared to operate this in a virtual environment to date.