Now that we understand how to assess the project risk, we are ready to actually plan and manage our test rounds. Since software development is a dynamic process, each level of testing must allow a great amount of flexibility. Offering all testing methods and types at each level gives the quality assurance manager the ability
“What gets measured gets managed and what gets managed gets done.” – Peter Drucker Before the project is organized and critical numbers are calculated, I recommend running a risk assessment exposing weaknesses in your quality assurance planning and processes. This analysis is a great tool that identifies issues well in advance. The assessment is much easier
Professor Cem Kaner J.D., PhD explains the “Impossibility of Complete Testing” in his lecture notes. This lecture mathematically demonstrates how impossible it to test all the options of a given set of enhancements. The testing straggly is to identify the areas that are most likely to pose issues and to develop and apply test cases
Thus far we have discussed two fundamental areas of testing software. These are Architecting the Environment (Principles behind setting up hardware environments.) Quality Assurance Management (Principles behind managing QA projects.) Now we are ready to discuss Managing Software Quality Assurance Test Rounds (Principles and examples for managing testing rounds.) Each test round is a separate
