The test of the auditing functionality of RAP has now completed full testing. The test included the pollution of the target database with sporadic record level updates against a number of the files to show how the audit functions will pick up the corruption between the systems. We also ran full object level Audits that check the objects between systems to ensure the code changes we made in the programs worked.
The data level tests consisted of an initial File/Mbr based check to ensure the functions return the correct CRC check sums for the source and target. Then we ran a program to create sporadic updates on the target before running the File/Mbr CRC checks again to ensure the corruption is identified correctly. Once we knew this was working we ran a Record level Audit with the Repair option set to *NO, this showed us the RRN’s of the records which were supposedly out of sync and prints them out to an audit report. Then we ran the Record level Audit again with the repair option *YES, the report which is generated shows the RRN’s which had been repaired so we could match this with the initial report to ensure the same records have been identified and repaired. So far everything showed the process was working and the records were back in synch, all we had to do to verify this was to run the File/Mbr level Audits again which showed as we expected no errors between the systems.
We did run a few more Record level Audits for other functionality checks such as ending the Audits while they were midstream to check the reporting messages and final report generation which all came back clean!
The Object Audits simply required changing a few attributes of objects between the systems to see if they were picked up by the process. This was eventually carried out on the target because after we updated objects on the source and ran the Audits they came back clean! Unfortunately (or fortunately depending on your perspective) the replication process had brought the objects back into sync which returned an unexpected result. Other than that we had no more surprises with the tests and everything we expected to be picked up was. After replicating the objects from the source to the target again the Audits came back clean.
As this was the biggest change since the last unit test code level, we feel pretty confident we can get the new release out before the end of the month again. The biggest challenge facing us now is the dreaded documentation!
If you would like to help us test the latest release before the GA release let us know.
Chris…