Seite - 99 - in The Future of Software Quality Assurance

Measure Twice, Cut Once: Acceptance Testing 99 Fig. 1 Primary approach toacceptance testing 3.2 BasicSteps toOrganizeaWell-DoneAcceptance Phase Having seen what the primary approach and being ignorant of it, let’s say, you are about to take thebasic steps to organizeawell-doneacceptancephase.Evenbefore taking them, you must make sure that you have in yourpocket all the prerequisites needed tostart, suchas: 1. Business requirementsareavailableand theyarenot incompleteorambiguous. 2. Theapplicationcode is fullydeveloped. 3. All other types of testing such as unit, integration and system testing are completed. 4. There are no show stoppersor high or medium defects in the system integration testing phase. 5. Youmusthaveonly theso called“cosmetic”errorsbeforeacceptance testing. 6. Regression testingshouldbecompletedwithnomajordefects. 7. All reporteddefectsare supposedto befixedandretested. 8. Theacceptance testingenvironmentmust be ready. 9. Sign-offmailorcommunicationmust beevident. 3.3 Approaches toCreateAcceptance Test Cases Afteryouhavemadesurethatyourrequirementsarepresent,clearandcomplete,the next step is to start writing the acceptance test cases. There are several approaches to do so, and what is advisable is a mix of them. The approaches that you should