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
Now that the system has been tested by the developer during their unit tests, the load test is complete and the quality assurance team has successfully executed their standard and new test cases, we are ready for our restaurant’s “Pre-Opening Reception”. The acceptance test is a purely black box test. The end user should focus
Integration testing is the most extensive level and the one which requires the largest portion of the test plan. At this point you should plan for a full regression test as well as functional testing to insure new features work as expected. This level of testing requires running all existing test cases from your script
