Acceptance testing is a level of software testing which determines whether the developed product is as per specified requirement or not. Acceptance testing is done by user or customer but at the same time stakeholders are also involved in acceptance testing. In acceptance testing user review or feedback is of much importance.
The goal of acceptance testing is to establish confidence in the developed system or product.
1. User acceptance Testing:
In user acceptance testing main focus is given on functionality of developed product, its fitness for use. As discussed earlier user acceptance testing is done by user or customer and application manager.
2. The Operational Acceptance test:
Operational Acceptance test also known as production test, it makes sure that the live build is working as intended in its new and final environment. This testing is done when all other testing phases are completed and a build is released into production. In most of the organizations production test is carried out by a system administrator before the system is released. Testing of backup/restore, disaster recovery, maintenance tasks is done under operational acceptance test. Operational acceptance test also involves periodic check of security vulnerabilities.
3. Contract Acceptance testing:
Contract acceptance testing is done against contract’s acceptance criteria for developing custom software. Before starting contract acceptance testing Acceptance should be formally defined when the contract is agreed.
4. Regulation Acceptance Testing
Regulation Acceptance Testing, also known as Compliance Acceptance Testing, examines whether the software complies with the regulations. This includes governmental and legal regulations.
5. Alpha Testing
Alpha testing is a type of testing in which developed software or application is tested before release. Alpha testing is done at developer’s site i.e. within the company and is typically performed by a group that is independent of the design team
6. Beta testing
Beta testing is a final round of testing which is done before releasing developed software to end users. Generally beta testing happens at customer’s site. In beta testing the developed application is given to end user for testing and their experiences are forwarded back to the developers who make final changes before releasing the software officially.
7. Black box Testing
Black box is a software testing method in which functionalities of developed applications are tested as per specification hence it is also called as specification based testing.
Black box tester does not need to know internal code of application. Main focus in black box testing is on functionality of the system as a whole.
1. To test if the need of customer is satisfied.
2. Is system fit for use?
2. Role Responsibilities:-
3. Technique used:-
1. Black box
4. Types of defects:-
1. Operational defects (Environment Related)
2. Usage Related.
5. Test Basis:-
1. User requirement specification (URS)/System requirement specification (SRS).
Exit for system test is satisfied.
7. Exit Criteria:-
When acceptance criteria is met.
Tools as required.
9. Output Document:-
1. Acceptance test log (ATL)
2. Acceptance test report (ATR)
3. Acceptance Report.