Content deleted Content added
m sp |
No edit summary |
||
Line 1:
{{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,
| |||