Operational acceptance testing: Difference between revisions

Revision as of 00:20, 13 March 2015

Revision as of 00:25, 13 March 2015

Line 2:

'''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 periodic check of security vulnerabilities.,<ref>ITSQB http://istqbexamcertification.com/what-is-acceptance-testing/</ref> and a White Paper on Operational Acceptance Testing, an evaluation of ISO 25000 SQuaREand vsOperational ISO 29119 SoftwareAcceptance Testing by AnthonyDirk WoodsDach et al., OAT generally subsumesincludes:<ref>Whitepaper: Operational Acceptance Testing. January 2015 Anthony Woods, Capgemini</ref>

* Maintainability Testing

* Accessibility Testing

:* including IT Service Management (Supportability)

* Backup / Recovery Testing

* Installation and Backout

* Code Analysis

* CompatibilityComponent Testing

* Performance, TestingStress and Volume,

* Conversion Testing

* Security Testingand Penetration

* Disaster Recovery (across data centres)

* Backup and Restoration

* Failover Testing (withinWithin the same data centre)

* Installability Testing

:* Component fail-over

* Interoperability Testing

:* Network fail-over

* Localization Testing

* Disaster Recovery (across data centres)

* Maintainability Testing

:* Data recovery

* Performance Testing

:* Application/system recovery

* Portability Testing

* Monitoring and Alerts (to ensure proper alerts are configured in the system if something goes wrong)

* Procedure Testing

:* including IT Service Management

* Reliability Testing

* Security Testing

* Stability Testing

* Usability Testing

During OAT changes may be 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. Typically OAT occurs after [[user acceptance testing]] (UAT), it is a final verification before a system is released.