Operational acceptance testing: Difference between revisions

Revision as of 14:30, 26 January 2011

Revision as of 09:30, 10 March 2011

Line 1:

'''Operational Acceptance Testing (OAT)''' is a 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 is not be included or merged in OAT.

{{Inappropriate tone|date=October 2010}}

'''Operational Acceptance Testing (OAT)''' is a new type of [[testing]] in the market. This is nowadays in very much demand in [[support]] and [[maintenance]] type projects. In this type of testing we only concentrate about the [[operational readiness]] of the system which would be supported or become the [[production environment]] later. Hence, it is also known as operational readiness testing. '''The [[functional testing]] of application should not be included or merged in OAT'''. This may include checking the backup facilities, maintenance and [[disaster recovery]] procedures. In OAT we play with those environmental things which our application uses to run smoothly. For a mixed/ hybrid architecture application, this may include: [[window services]], [[config file]]s, [[web services]], [[XML file]]s, [[COM+]] components, web services, [[IIS]], stored procedures in databases, etc. This type of testing should be conducted before the user acceptance testing.

The approach to be used in OAT is:

# Build the system,

# Deploy the application,

# Supportability of the system.

# Validate the [[backup procedure]]s setup for system

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, [[IIS]], stored procedures in databases, etc. This type of testing is conducted before [[user acceptance testing]].

Then check how our application is behaving and moreover how our system is behaving in these conditions? Are the backup procedures setup for [[emergency situation]] working properly?

The approach to be used in OAT isincludes these steps:

For running the OAT [[test case]]s, the tester should have exclusive access to the system/ environment. This means that a single tester would be executing the test cases at a single point of time. For OAT we should define the exact OR quality gates; Entry and Exit Gate. This should list down all the activities which would be part and covered in the different phases of testing. The main emphasis should be on the operational part of the system.

#* Build the system,

{{Uncategorized|date=October 2010}}

#* Deploy the application,

#* Supportability of the system.

#* Validate the [[backup procedure]]s setup for the system

Then checkchecks are made on how ourthe application is behaving, and moreover how ourthe system is behaving as a whole in these conditions?. AreBackup theprocedures backupare proceduresalso setupchecked forto [[emergencyensure situation]]proper workingoperation properly?under emergency conditions.

For running the OAT [[test case]]s, the tester shouldnormally havehas 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 we should define the exact OR quality gates; are defined, both Entry and Exit Gate. ThisAll shouldactivities listare down all the activitieslisted which would be part and covered in the different phases of testing., Thewith mainprimary emphasis should be on the operational part of the system.

[[Category:Software testing]]