Strive for Quality in System Testing: A Top 10 List

Finding non-functional, system level problems before a system is delivered-and early enough to allow for low cost corrections-is a perennial testing issue. You need a systematic approach to system testing that keeps key system test objectives visible and assigns the correct priority among other test activities. Based on his team's experiences at IBM, Jerry Cobry describes how there needs to be a special mindset for system testing and describes some of the challenges they faced. Then, using the mnemonic STRIVE FOR Quality, Jerry describes key factors for successful system testing: Stress, Time, Resources, Interaction, Volume, Environment, Focus, Operational profiles, Randomness, and Quality. Go beyond simply finding system problems and become a product assessment engineer. Question your old ways of doing things, get out of your comfort zone, and strive for quality in conducting your own system tests.