The Main Goal of Acceptance Testing

by Nataliia Vasylyna | October 5, 2011 10:00 am

The main goal of acceptance testing[1] is to check that the pre-concerted software requirements have been satisfied.

Acceptance testing is the amenability of the customer; is conducted independently from the software development activity; and is separate from the design verifications and system testing.

Acceptance Testing is similar to System Testing in that it tests the system as a whole. Nevertheless, it is unlike system testing in two significant ways.

The accepting organization (the customer) is answerable for performing the test and defining the test results.

So the purpose of the Acceptance Testing is not to look for defects, but to create customer certainty that the system works correctly and is ready for handover. In such a way, Acceptance Testing may be more of a demonstration and proof of an accurate work than a software testing[2].

Since Acceptance Testing is customer amenability, the customer may request to utilize some tests already developed for use in System Testing.

Related Posts:

Endnotes:
  1. acceptance testing: http://qatestlab.com/services/service-models/acceptance-testing/
  2. software testing: http://qatestlab.com/company/why-software-testing/
  3. Acceptance Criteria vs Acceptance Test: http://blog.qatestlab.com/2017/04/06/criteria-acceptance-tests/
  4. How to Build Acceptance Tests?: http://blog.qatestlab.com/2015/01/14/how-to-create-efficient-build-acceptance-tests/
  5. Acceptance Testing and Software Release: http://blog.qatestlab.com/2012/03/12/acceptance-testing-and-software-product-release/
  6. Briefly about System Testing: http://blog.qatestlab.com/2017/02/28/system-testing-specifics/
  7. Peculiarities of Testing Levels: http://blog.qatestlab.com/2016/02/15/testing-levels-peculiarities/

Source URL: https://blog.qatestlab.com/2011/10/05/the-main-goal-of-acceptance-testing/