Testing via ISO images
I have some questions for ya'll.
In my testing environment for a particular project that I'm working on, we have multiple feature sets being built for each build, each SKU with more features than the previous. THis forces QA or the build guy to burn CDs for each SKU, which means 2-4 cd's per SKU, plus one SKu that is DVD.
I suggested, since we create ISO images befor eburning the cd's, that we just use a central machine to mount the images and serve them across our network, keeping an eye on the ISOs so they don't expand over the 650mb production limit. I was shot back with "That is not a real qorld scenario".
So, how is this not a real world scenario, and how could I convince my coworkers/boss that this IS a functional test? I mean, the ISO *IS* the cd fo rth emost part, and i fthe ISO can be mounted and seen, it's bit identical to a physical CD. I've even found that some ISos were built incorrectly in less time than it took my coworkers to burn a coaster and find out it didn't work.
Am I totally out of line here, just trying to cut corners and speed things up unnecessarily, or shoul dI continue to try to hammer this across?
Thanks in advance!
Re: Testing via ISO images
I don't think you are totally out of line at all.
There's certainly no need to physically burn CDs and DVDs for every internal build.
But of course, you'd want to burn disks before a build destined for external use.
In the past, I've done exactly what you are proposing - leave media tests until near the end of the development cycle, while keeping an eye on the size of the images as you go along.
How do you convince your boss? I don't know - show them this thread, perhaps?