Operational acceptance testing: Difference between revisions

Revision as of 05:40, 20 June 2015

Revision as of 17:10, 5 March 2016

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 Acceptanceacceptance Testingtesting (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 development]] and [[software maintenance]] projects. This type of testing focuses on the [[operational readiness]] of the system to be supported, and/or to become part of the production environment. Hence, it is also known as '''operational readiness testing''' (ORT) or [[operations readiness and assurance]] (OR&A) testing. [[Functional testing]] within OAT is limited to those tests which are required to verify the ''non-functional'' aspects of the system.

According to the International Software Testing Qualifications Board (ISTQB), OAT may include checking the [[backup]]/restore facilities, IT [[disaster recovery]] procedures, maintenance tasks and periodic check of security vulnerabilities.,<ref>ITSQB http://istqbexamcertification.com/what-is-acceptance-testing/</ref> and whitepapers on ISO 29119 and Operational Acceptance by Anthony Woods,<ref name="ISO 29119 OAT">{{cite paper|author=Anthony Woods|title=Operational Acceptance - an application of the ISO 29119 Software Testing standard|date=2015}}</ref> and ISO 25000 and Operational Acceptance Testing by Dirk Dach et al., OAT generally includes:<ref>White Paper: Operational Acceptance Testing, Business Continuity Assurance. December 2012 Dirk Dach, Dr Kai-Uwe Gawlik, Mark Mevert</ref>