Content deleted Content added
Usa63woods (talk | contribs) This article was so far single platform focused it tended to be wrong more often than right; so I fixed it. |
m WP:CHECKWIKI error fixes + other fixes using AWB (9918) |
||
Line 1:
[[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 operational readiness (pre-release) of a product, service or system as part of a [[quality management system]]. OAT is a common type of non-functional [[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''' (ORT). [[Functional testing]] of applications is not to be included or merged in OAT.
According to the International Software Testing Qualifications Board (ISTQB), OAT may include checking the [[backup]]/restore facilities, IT [[disaster recovery]] procedures, maintenance tasks and and periodic check of security vulnerabilities.
* Maintainability
Line 27:
* Validate the backup and recovery procedures for the system
For running the OAT [[test case]]s, 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.
[[Category:Software testing]]▼
{{reflist}}
▲[[Category:Software testing]]
| |||