Quality Assurance Planning – Part Three (Acceptance Testing)

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

Quality Assurance Planning – Part Two (Integration & System Testing)

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

Quality Assurance Planning – Part One (Unit Testing)

Unit testing should be done by the developer and include two tests. The first of these is to walk through each line of his code to insure it works correctly. This is a normal part of the development process, however the second test is not. During this test the developer should try to “break” their