Operational acceptance testing
Operational acceptance testing (OAT) is a type of software testing, used mainly in software support and software maintenance projects. This type of testing focuses on the operational readiness of the system to be supported, or which is to become the production environment. Hence, it is also known as operational readiness testing. Functional testing of applications is not be included or merged in OAT.
It may include checking the backup facilities, maintenance and disaster recovery procedures. In OAT changes are made to environmental parameters which the application uses to run smoothly. For example, with Microsoft Windows applications with a mixed or hybrid architecture, this may include: Windows services, configuration files, web services, XML files, COM+ components, web services, IIS, stored procedures in databases, etc. This type of testing is conducted before user acceptance testing.
The approach used in OAT includes these steps:
- Build the system,
- Deploy the application,
- Supportability of the system.
- Validate the backup procedure setup for the system
Then checks are made on how the application is behaving, and moreover how the system is behaving as a whole in these conditions. Backup procedures are also checked to ensure proper operation under emergency conditions.
For running the OAT test cases, the tester normally has exclusive access to the system or environment. This means that a single tester would be executing the test cases at a single point of time. For OAT the exact OR quality gates are defined, both entry and exit gate. All activities are listed which would be part and covered in the different phases of testing, with primary emphasis be on the operational part of the system.
There are various aspects of OAT –
- Fail over testing (resilliance testing)
- Component fail-over
- Network fail-over
- Alerting/alarming (to ensure proper alerts are configured in the system if something goes wrong)
- Backup and recovery testing – to ensure that backup and recovery is successful
Wikimedia Foundation. 2010.
Look at other dictionaries:
Acceptance testing — of an aircraft catapult In engineering and its various … Wikipedia
Software testing — is an empirical investigation conducted to provide stakeholders with information about the quality of the product or service under test [ [http://www.kaner.com/pdfs/ETatQAI.pdf Exploratory Testing] , Cem Kaner, Florida Institute of Technology,… … Wikipedia
Supermarine Spitfire operational history — November 1942 photo of a very early Mk IXb of 306 (Polish) Toruński Squadron. Main article: Supermarine Spitfire The Supermarine Spitfire, the only British fighter to be manufactured before, during and after the Second World War, was designed as… … Wikipedia
List of computing and IT abbreviations — This is a list of computing and IT acronyms and abbreviations. Contents: 0–9 A B C D E F G H I J K L M N O P Q R S T U V W X Y … Wikipedia
Oat (disambiguation) — Oat may refer to: Oat Plural: Oats Cereal Ohio Achievement Test Optometry Admission Test (O.A.T.) Organic Anion Transporter Oxford Aviation Training Overseas Adventure Travel Organic Acid Technology (antifreeze) Obligation assimilable du Trésor… … Wikipedia
Area 51 — This article is about the U.S. Air Force installation in Nevada. For other uses, see Area 51 (disambiguation). Area 51 … Wikipedia
Mikoyan-Gurevich MiG-3 — MiG 3 Soviet Air Force MiG 3s in winter camouflage. The slogan on the nearest aircraft reads Za Rod … Wikipedia
Vought F6U Pirate — F6U Pirate Role Fighter aircraft Manufacturer Chance Vought First flight … Wikipedia
Bell P-39 Airacobra — P 39 Airacobra P 39Q 1BE 42 19447, Saga Boy II of Lt. Col. Edwin S. Chickering, CO 357th Fighter Group, July 1943 Role Fighter … Wikipedia
Avro Vulcan — Infobox Aircraft name= Avro Vulcan caption= A Vulcan B.2 of the RAF type= Strategic bomber national origin = United Kingdom manufacturer= Avro designer= first flight= 30 August 1952 introduction= 1956 retired= March 1984 status= primary user=… … Wikipedia