Measure Twice, Cut Once: Acceptance Testing

2Citations
Citations of this article
4Readers
Mendeley users who have this article in their library.

This article is free to access.

Abstract

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 knowledge but also demands to be able to put themselves in the user’s shoes. Being aware of the problems that will be met and relying on the testing performed so far, many decide to skip the need for conducting acceptance testing using both external 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”-the end user, who is now to judge even harshly as ever, because of all the possibilities he/she has and the ease of switching from one software to another. That is the reason each project manager must be aware of the main challenges of organizing and conducting the acceptance testing. The benefits from it are numerous 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 follow the release of a lousy product in the eyes of the end user.

Cite

CITATION STYLE

APA

Mitev, M. (2019). Measure Twice, Cut Once: Acceptance Testing. In The Future of Software Quality Assurance (pp. 93–104). Springer International Publishing. https://doi.org/10.1007/978-3-030-29509-7_7

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free