Page - 100 - in The Future of Software Quality Assurance

100 M.Mitev definitelytake intoaccountare thetestcases thatarerequirementsbased(traditional approach),businessprocess/workflowanddata drivenapproach. Why we advise you to use more than just one approach? Because if you use onlythe traditionalrequirements-basedapproach,thenthe testcasesyoucreatemay also carryover the defectsof the requirements. Inaddition to that when incomplete and incorrect requirementsarepresent, thenyour test casesbecomeincompleteand incorrect. The downside of the business process/workflow test cases is that data- relatedtesting isoutof its scope.Andthedata-drivenonesfocusheavilyonthedata andmissout the processand thebusiness side. Also, never forget that writing the acceptance test cases is not the last step of system development.Writing them starts right after the completionand approvalof the requirements,data models and applicationmodels, and before the development is completed. The tips we can give you when you start planning the acceptance testing phase are: 1. Identify and involve the key users—they have a deep understanding of the user requirements. 2. Providenotonlydemobutalsoa hands-ontrainingof thesystem to theusers. 3. Have the userswrite theirown test casesaswell. 4. Ensure that theuserswill alsoexecute the tests. More specifically, it is very important to clearly identify and set SMART boundaries of the roles, the type of testing to be executed—in person or self- paced—and the time frames (as you are aware time is never enough to perform a thorough testing), to set the documentation standards and determine the change controlprocess. 3.4 Roles andResponsibilities Therolesare similar to theone in theScrumteam—youshouldhaveanOwner/PM who will manage the process and take the final decisions within the team. The Owner will also update the project sponsoron the status. Then, the project sponsor orBusiness Ownercomes.She/hewill take careof the requirementsandwill assist the Owner/PM when testing them. That person will also be solely responsible for the Change Control process. The team resources will actually do the acceptance testing.