Acceptance testing is performed by customers or their representatives after system testing to determine if the system meets their needs and expectations. Acceptance tests execute real-life scenarios near the customer environment and have a small number of test cases intended to validate functionality, not find defects. Customers verify that the product, procedures, user documentation and service level agreements all meet acceptance criteria before the product is approved for release.

1. Acceptance testing

2. • Acceptance testing is a phase after system testing that is
normally done by the customers or representative of the
customer.
• Acceptance test is performed by the client, not by the
developer.
• Acceptance test cases are normally small in number and
are not written with the intention of finding defects.
• However, the purpose of this test is to enable customers
and users to determine if the system built really meets
their needs and expectations.
• Acceptance testing is done by the customer or by the
representative of the customer to check whether the
product is ready for use in the real-life environment
• Acceptance tests are written to execute near real-life
scenarios.

3. Acceptance Criteria.
• Product acceptance
– During the requirement phase each requirement is mapped with
acceptance criteria
– Acceptance test not to test with test cases that have not been tested
but testing with certain categories of test cases
• Procedure acceptance
– Acceptance criteria based o procedure followed for delivery
• User document and trouble shoot should be part of delivery
• Along binary code source code also to be delivered
• Minimum of 30 employees are trained on the product usage before
deployment
• Service level agreements(SLA)
– Important contract items are taken and verified as part of acceptance
testing
• All major defect that come up during the first 3 month need to be fixed free of
cost
• Downtime of the implemented system should be less than 0.1%
• All major defects fixed with in 48hrs of reporting

4. Selection test cases for Acceptance
Testing
• End-to-end functionality verification
– To ensure all the business transaction are tested as testing
• Domain tests
– Test cases that reflect business domain knowledge are included
• User scenario tests
– Acceptance testing reflect the real life user scenario verification
• Basic sanity tests
– Verify the basic existing behavior of the product are included
• New functionality
– When product in modification, test case focus on verifying new feature
• A few non-functionality
– Add few non- functional tests
• Tests pertaining to legal obligations and service level agreements
• Acceptance test data
– User customer’s real life data

5. Executing acceptance tests
• A acceptance test team comprise members who are all
involved in day to day activities of product usage.
• They may not know the technical aspect of software but
they know whether the product does what is intended to
do.
• 90% of them possessing required business process
knowledge and 10% being representatives of technical
testing team.
• # of member is less because effort and scope of testing is
less
• Before testing appropriate training need to be provided.
• Team member can get help from developing team too.

6. • Test team members help the acceptance
members to get requires test data, test case and
analysis acceptance test result.
• Defect are reported by the acceptance team
members during test execution.
• Test team members receive report and fix higher
priority defects necessarily fixed.
• Before release all resolution of those defects
discussed with acceptance team members and
get approval for concluding the completion of
acceptance testing.

7. When is it performed?
• Acceptance Testing is performed after System
Testing and before making the system
available for actual use.

8. Who performs it?
• Internal Acceptance Testing (Also known as Alpha Testing)
– is performed by members of the organization that developed the
software but who are not directly involved in the project
(Development or Testing). Usually, it is the members of Product
Management, Sales and/or Customer Support.
• External Acceptance Testing
– is performed by people who are not employees of the organization
that developed the software.
• Customer Acceptance Testing is performed by the customers of the organization
that developed the software. They are the ones who asked the organization to
develop the software.
• User Acceptance Testing (Also known as Beta Testing) is performed by the end users
of the software. They can be the customers themselves or the customers‘
customers.