I am currently testing just software functions, but we also test installations of hardware and of software so that we can document the parameters we use. That helps us speed-up trouble-shooting, as well as standing up new equipment or software updates.
We test as thoroughly as possible. It takes more time to roll-out new things, but we have little drama when we do the roll-out. I still struggle to defend the time it takes for these tests, though. Testing is iterative, and good testing should find as many flaws as possible (errors and design flaws) and cannot end until every thing is correct. Clear and concise requirements are necessary for proper design and testing. I used to be in charge of hardware and software for a large Defense contract, though. We had to show an exhaustive set of tests for all hardware and software before it was accepted, so I am familiar with that as well. Apple also knows designing/selecting and testing both hardware and software. That has shown to be a big advantage over MS, in both the Zune-iPod/iPhone as well as OS X-Vista. Thank you, Mark Snyder -----Original Message----- > I am currently the test manager for an enterprise system. > We test every functional requirement. Rigorous testing is a requirement, and I'm certainly not suggesting otherwise. The company I do most of my consulting for is extremely aggressive in its testing. But are you saying that you manufacture hardware, and that you test every function of every hardware component that you purchase from third parties? Because that is what we're talking about. If so, your company is one in a million and I salute you. ************************************************************************* ** List info, subscription management, list rules, archives, privacy ** ** policy, calmness, a member map, and more at http://www.cguys.org/ ** *************************************************************************
