Seite - 93 - in The Future of Software Quality Assurance

MeasureTwice,CutOnce: Acceptance Testing MitkoMitev Abstract The challenges it sets are numerous and thus, many project managers facetheharddecisionofhowtoorganizetheprocessthatrequiresnotonlytechnical knowledgebutalsodemands tobeable toput themselves in theuser’sshoes.Being aware of the problems that will be met and relying on the testing performedso far, manydecide to skip the need forconductingacceptance testing usingbothexternal and internal resources. And what happens next—great loss for the company as the end user is dissatisfied with the software and refuses to use it. The company will face not only profit loss, but what is more important in the modern world: loss of reputation and credibility among partners, competitors and above all—“his/her majesty”—theenduser,whoisnowtojudgeevenharshlyasever,becauseofall the possibilitieshe/shehasand theease of switching fromonesoftware to another. That is the reasoneachprojectmanagermustbeawareof themainchallengesof organizingandconductingtheacceptancetesting.Thebenefitsfromitarenumerous and will only lead you and your team to a greater success. Of course, it should be performed correctly and planned really well; otherwise you will have to deal with the losses that followthe releaseofa lousyproduct in theeyesof the enduser. Keywords Software testing · Softwarequality · Software tester · Acceptance testing 1 Acceptance Testing,Part 1: Introduction Oftenneglected,one of the most importantphases in makingsure that the software meets theuser requirements is acceptance testing. The challenges it sets are numerous and, thus, many project managers face the hard decision of how to organize the process that requires not only technical knowledgebutalsodemands tobeable toput themselves in theuser’sshoes.Being M.Mitev SEETB, QualityHouse Bulgaria, Sofia, Bulgaria ©The Author(s) 2020 S.Goericke (ed.), The Future of Software QualityAssurance, https://doi.org/10.1007/978-3-030-29509-7_7 93