5 Automated Testing Procedure
Following is the suggested sequence of steps that would need to be performed on a daily basis as part of the Automated Testing.
Table 5-1 Automated Testing Procedure
| Day 1 |
|---|
| Test Database to be refreshed with Production values * |
| 1. Truncate the Log tables in Production |
| 2. Logging is Turned On in Production after last job has completed |
| Cut off time for manual transactions/user activities in the Production Environment. Logging by testing tool will be turned off. |
| 1. Take a Production database snapshot (S1) of the required tables |
| 2. Ensure sequences on test match sequences on Production (for applications and accounts) |
| 3. Dat files and log tables are moved to the Test database |
| 4. Testing tool is Run on Test instance (Ensure previous files are removed) |
| Comparison/Validation scripts are run against S1 and the Test database. Report (R1) is generated. (This gives us the comparison before the jobs are run) |
| A copy of input file in Production (lockbox) should be available in Test |
| Batch jobs are run (Batch job setup is identical to production) on both Test & Production |
| Take a Production database snapshot (S2) of the required tables |
| Comparison Scripts are run against S2 and the Test database. Report (R2) is generated. (This gives us the comparison before the jobs are run) |
| Day 2 |
| Validates R1 & R2 and reports discrepancies to OFSLL |
| Investigate the discrepancies. Some may be reconciled and some may require a fix |
| Manual testing proceeds in the interim |
| Next run is planned |
| Test Database to be refreshed with Production values. |
* Refresh Test database
Example: To run the testing tool in the Test environment on 4/23, a snapshot of the Production database AFTER the batch jobs have completed on the morning of 4/23 and before any other user activity for 4/23 begins needs to be taken. This snapshot will be used to refresh the test database for the testing tool to be run on the evening of 4/23.