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
In his reconstruction speech given to Congress on April 11, 1865, Abraham Lincoln warned the nation that creating inflexible plans will, “…become a new entanglement”. The quality assurance manager can draw a number of lessons from the broader context of the speech. Here is the complete thought. …so new and unprecedented is the whole case,
You will become better at planning your test cycles the more often you execute them. There is no substitute for experience. A plan is basically a prioritized list of tasks assigned to a resource. A plan is like a noun. It describes but accomplishes nothing. It is the schedule that moves your plan into action.
Here is how I break-down quality assurance types and what questions I ask to determine which should be included in the test cycle: Development (Have the coding architectural errors been identified and resolved? This can only done as a white box test and requires a code review.) Installation (Does the application come on line after
