Operational acceptance testing: Difference between revisions

Revision as of 08:14, 31 May 2012

Revision as of 10:00, 25 September 2012

Line 2:

[[File:US Navy 070804-N-1745W-122 A Sailor assigned to Aircraft Intermediate Maintenance Department (AIMD) tests an aircraft jet engine for defects while performing Jet Engine Test Instrumentation, (JETI) Certification-Engine Runs.jpg|right|thumb|250px|Operational testing a jet engine]]

'''Operational acceptance testing (OAT)''' is used to conduct [[Performanceoperational testreadiness (assessmentpre-release)|performance testing]] of a product, service or system as part of a [[quality management system]]. OAT is a common 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]]{{dn|date=May 2012}}. Hence, it is also known as '''operational readiness testing'''. [[Functional testing]] of applications is not to 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 service]]s, [[configuration file]]s, [[web services]], [[XML]] files, [[COM+]] components, web services, [[Internet Information Services|IIS]], stored procedures in databases, etc. This type of testing is conducted before [[user acceptance testing]].