Operational Acceptance Testing

There are several types of Operational Test Activities that may be considered for a testing purpose, but the most important ones are as i have discussed below. These are discussed and defined from my own experience of work:

a)   Application fail-over Test

         ·         Objective:

a.      To ensure whether resilience node is capable to handle the load when one of the two nodes goes down and it shares the load successfully when it is back.

     b)   Database Failure Test

·         Objective:

a.      To ensure whether the proper DB Alerts are received when a Database is down.

b.      Time taken for restoration of service will be monitored during this test

     c)    Cable Pull Test (Network Blip Test)

          ·         Objective:

a.      The objective of this test is to do Network Blip testing and Application servers’ recover-ability.

d)   UNIX Failure Test

          ·         Objective:

a.      The objective of this test is to verify the behavior of UNIX Application servers if they crash (abrupt shutdown).

  

e)   Creation & Dropping of Partition Test

          ·         Objective:

a.      To ensure there is no performance impact while creating and dropping partitions on the database

f)     Connection Keep Alive Test

          ·         Objective:

a.      The objective of this test is to verify the behavior of application connections when left idle for long

  

       g)      Back-end Failure Test

·         Objective:

a.      The objective of this test is to verify the behavior of applications when Back-end systems go unavailable & return back online.

b.      All back-end systems involved will be made unavailable one by one.

        h)      Back-end Fail-over Test

·         Objective:

a.      The objective of this test is to ensure that back-end is capable to handle the request on Secondary Web Service when Primary Web Service is down.

b.      All back-end systems involved will be tested for this one by one.