Scribd
Upload
44 views3 pages

Acceptance Testing Vs User Acceptance Testing

Acceptance testing and user acceptance testing are both parts of the software testing process, but they differ in important ways. Acceptance testing checks if the software meets requirements and criteria for acceptance, while user acceptance testing specifically involves end users testing the software to determine if they will accept it. User acceptance testing has an unlimited scope for identifying issues compared to automated testing, and is critical for real acceptance even if automated testing passes, as users may reject software that is functionally sound. Both aim for client satisfaction overall.

Uploaded by

Joy Bose
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
44 views3 pages

Acceptance Testing Vs User Acceptance Testing

Acceptance testing and user acceptance testing are both parts of the software testing process, but they differ in important ways. Acceptance testing checks if the software meets requirements and criteria for acceptance, while user acceptance testing specifically involves end users testing the software to determine if they will accept it. User acceptance testing has an unlimited scope for identifying issues compared to automated testing, and is critical for real acceptance even if automated testing passes, as users may reject software that is functionally sound. Both aim for client satisfaction overall.

Uploaded by

Joy Bose
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Acceptance Testing VS User Acceptance

Testing: Same or different

Acceptance testing is the last step in software testing. The software here is tested and it is checked
whether it will be “Accepted” by the customer or not. Hence the name acceptance testing. Formal
testing regarding client needs, prerequisites, and business forms directed to decide if a framework
fulfills the acknowledgment criteria and to empower the client, clients or other approved element to
decide if to acknowledge the software. It is the last stage of software testing which comes after the
system testing. It is done just before the release of the software. User Acceptance testing is a part of
Acceptance testing and it is a new concept brought in the software testing field.

Following are the types of Acceptance Testing

• Operational Acceptance Testing


• Contract and Regulation Acceptance Testing

• Factory Acceptance Testing

• Alpha and Beta Testing

• User Acceptance Testing

It can be said that User Acceptance Testing is the last process in Acceptance Testing because after the
software is ready to launch and all the technical problems are resolved through another testing, the user
acceptance testing remains where it depends upon the customer whether they’ll accept the software or
not.

Let's take an example of User Acceptance Testing

Assume that Facebook has launched a new feature in which you can send postcards through Facebook.
Everything went well in the functional testing, the developers tested the feature and it was working.
When this feature was sent for user testing, most the users who were the testers didn’t like the feature
and rejected it. So, the feature which was developed was technically sound but it became a failure in the
practical world. The importance of User Acceptance has increased drastically.

Even though User Acceptance testing is a part of Acceptance testing/functional testing, there are few
differences in them.

These differences are as follows

1. Computer vs human – The basic difference in these tests is that one test is conducted by a computer
and the other test is conducted by a human. In functional testing, the computer checks all that whether
all the processes are running without any error. For example, a website is created, but the loading
screen takes a lot of time to load, the computer won’t be able to point out this problem but with User
acceptance testing, this problem is easily detected.

2. Unlimited Scope – With User acceptance testing the scope of betterment in the software is
unlimited because, in user testing, a user will be able to point out the problems pragmatically.

3. Real Acceptance – It doesn’t matter if the software is cleared in functional testing unless and until it
gets through the User acceptance testing. If the software fails in the user acceptance testing, then it
would be clear that the software is usable even though it is fully functional.

4. Contract and Regulation Acceptance Testing – This type of acceptance testing is a part of user
testing where the legality of the software is checked. It is checked whether the software can be legally
upheld.

User acceptance testing has proved to be an important part of acceptance testing. Functional testing is a
different type of testing and User acceptance is another type of testing. They are not really comparable
with each other because they are part of the same process. The main aim of both of these tests is client
satisfaction.

You might also like