For more information please visit http://appium-selenium.com/

1. ACCEPTANCE
TESTING
http://appium-selenium.com/

2. ACCEPTANCE TESTING
• After System testing the system will be delivered to the user or
customer for acceptance testing
• Testing done on environment similar to of production
• It involves black box testing for product
• Testing establish confidence in the system
• Testing done by independent testers, user and other stakeholders
• Acceptance testing is most often focused on a validation type of
testing i.e. system fit for use
• The goal of acceptance testing is to establish confidence in the
system
Component
Testing
Integration
Testing
System
Testing
Acceptance
Testing
http://appium-selenium.com/

3. ACCEPTANCE TESTING CONTD.
• Customer verifies if acceptance testing is passed
• The acceptance test should answer questions such as:
1. Can the system be released?
2. What, if any, are the outstanding (business) risks
3. Has development met their obligations?
• Testing is done at different levels:
1. A Commercial Off The Shelf (COTS) software product may be
acceptance tested when it is installed or integrated
2. Acceptance testing of the usability of a component may be done
during component testing
3. Acceptance testing of a new functional enhancement may come
before system testing
http://appium-selenium.com/

4. ACCEPTANCE TESTING CONTD.
• Types of Acceptance testing
1. Compliance acceptance testing: contract, regulations, laws
2. Operational/Production acceptance test: system meets the
requirements for operation
3. User Acceptance testing: Alpha/Beta testing
http://appium-selenium.com/

5. THANKS
http://appium-selenium.com/