Testing process where a system is tested for acceptability by stakeholders/users. The purpose of this test is to evaluate the system’s compliance with the business requirements and assess whether it is acceptable for delivery.
Some features of Acceptance testing are :
- Done to gain confidence in the system,specific non-functional characteristics of the system. Assess the system’s readiness for deployment and use.
- Acceptance is usually the last stage of testing
- Performed by end users and other stakeholders against the business scenarios.
- It aims to verify functional and non-functional requirements of the system, and data quality characteristics.
- It is one of the most important types of testing, as it confirms that application meets the intended specifications and satisfies the client’s requirement.
- The QA team will have a set of pre-written scenarios and test cases that will be used to test the application.
Types of Acceptance Testing:
User acceptance testing :
This type of testing verifies if a system is fit for use by business users.
Operational (acceptance) testing :
Done by system administrators, which includes activities like:
- backup/restore testing
- Disaster recovery
- Maintenance tests
- Data loading and migration
- Check of security vulnerabilities
Contract and Regulation Acceptance Testing:
This type of testing is to verify that the produced software satisfies the contractual agreement. Acceptance criteria should be defined when the parties agree to the contract.Such as government, legal or safety regulations.
Alpha Testing :
Alpha testing is performed at the developing organization’s site but not by the developing team.
Beta testing, or field-testing:
It is performed by customers or potential customers at their own locations.Beta testing is done by a limited number of end users before delivery, the change request would be fixed if the user gives feedback or reports defects.
Risk analysis reports
Fully integrated system
Operational and maintenance processes
|Customers or potential customers