Content deleted Content added
image |
change is to are and add the word to in the first paragrah at this point... applications are not to be included or merged in OAT. |
||
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 [[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]]. Hence, it is also known as '''operational readiness testing'''. [[Functional testing]] of applications
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]].
| |||