No, but I've found those kind of things while doing manual testing...and then I don't feel so bad when I miss a test scenario. It's not always that easy to second-guess users.
Don't look now but a QA Engineer just snuck in...
No, but I've found those kind of things while doing manual testing...and then I don't feel so bad when I miss a test scenario. It's not always that easy to second-guess users.
Don't look now but a QA Engineer just snuck in...
Whatever it is, it's usually not enough. But seriously, my work machine has an 80GB hard drive and I'm constantly having to manage it because it's almost full. Mostly with test and dev tools. I have 1T internal and external hard drives on my home machine and 250GB on my laptop. Much better. Meanwhile, software keeps getting bigger and more resource intensive, so it all seems relative...
I used Hyper-V quite extensively in my previous job and ran Debian Linux machines (literally my first experience with Linux) to test FTP, SFTP and FTPS adapters as well as Win 2008 Server/SQL Server 2008 machines to test installation of our web application. I took advantage of the network setup options to closely mimic the customer's configuration. Hyper-V has its quirks and in 2010 the interface wasn't as graphic as VMWare. But there are plenty of tutorials out there and once you learn to properly copy/clone the machines and maintain snapshots, it's very easy to use. Plus, as a QA Engineer, I loved having control of my test environment, knowing that I wouldn't have to worry about how someone else's changes to the environment might affect my testing. I haven't found Virtual Box to function as well on Windows but had decent experiences with it on Linux. And while VMWare has some advantages over Hyper-V, I'd probably go back to Hyper-V given the option.