Operational Acceptance Testing (OAT) is a type of software testing that is performed to conduct operational pre-release of a software, system or application to check the quality of it. Operational Acceptance Testing is a very usual software testing whose type is non-functional and it is mainly used in software development and software maintenance projects.
Operational Acceptance Testing mainly focuses on the operational readiness of the software and to become part of the production environment. Functional testing in operational acceptance testing is limited to the tests required to verify the non-functional aspects of the system.
Operational Acceptance Testing is also known as Operational Readiness Testing (ORT) or Operations Readiness and Assurance Testing (ORAT).
Objective of Operational Acceptance Testing:
The objective of Operational Acceptance Testing is:
- To determine resiliency of the software.
- To determine recovering ability of the software.
- To determine integrity of the software.
- To determine software can be deployed on a network on ITIL standards.
- To determine supportability of the software.
Operational Acceptance Testing Steps:
First step is designing the system as per the user requirements. The system is designed in such a way that it fulfills the end user requirements.
After the designing of the system, its designing is analyzed. It is analyzed that whether the system is according to user requirements and whether it will operate the way it is designed.
After the design of system is prepared and analysis is done, system construction phase starts. It is the main phase of operational acceptance testing.
System address evaluation:
Once the system building is finished, after that system address is evaluated and it is checked whether is according to user requirement.
After building and address evaluation of software, it is established according to perform the specific task for the purpose of which it is constructed.
System’s operability and supportability assess:
Now in the last phase the operability and supportability of the software system or application is tested. This leads to the end of whole procedure.
Types of Operational Acceptance Testing:
- Load Testing
- Performance Testing
- Installation Testing
- Backup and Restore Testing
- Security Testing
- Recovery Testing
- Difference between System Integration Testing (SIT) and User Acceptance Testing (UAT)
- Difference between System Testing and Acceptance Testing
- Acceptance Testing | Software Testing
- Software Engineering | Differences between Sanity Testing and Smoke Testing
- Software Engineering | Comparison between Regression Testing and Re-Testing
- Difference between Database Testing and Data warehouse Testing
- Difference between Agile Testing and Waterfall Testing
- Difference between Black Box Testing and Gray Box Testing
- Difference between Volume Testing and Load Testing
- Difference between Unit Testing and Integration Testing
- Difference between Stress Testing and Volume Testing
- Differences between White Box Testing and Gray Box Testing
- Difference between Active Testing and Passive Testing
- Difference between Cucumber Testing and Selenium Testing
- Difference between Frontend Testing and Backend Testing
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to email@example.com. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.
Improved By : nidhi_biet