A Process Framework to Control the Time of Software Acceptance Testing

Journal of ACS Advances in Computer Science · 2007

Acceptance testing is the formal testing phase used to demonstrate that thesoftware performs as required. This is the final stage in the testing process beforethe software is accepted for operational use.Acceptance testing is the responsibility of the customer. Nevertheless, it hasimportant implications on the project, as its duration impacts the cost and thepayment schedule.It is therefore important for both customer and software supplier to ensure thethoroughness of the acceptance test while minimizing its duration.The lack of coordination between acceptance testing and other testing phases( unit testing, integration testing, and system testing), in addition to customer’swish to build confidence in the software, lead to a substantial prolongation ofacceptance testing duration.In this paper, we discuss a practical approach to shorten the time of acceptancetesting, and we propose a framework for “good enough” testing derived from thefollowing basic ideas: Involving the customer early in the software testingactivities and consider the scope and results of the other testing activities whenplanning for acceptance testing.Combining acceptance testing with other testing activities will save time andmoney.

Read the paper · More papers on PaperTik