Breif summary of RA-Swiftconect Testing.

In first round of Testing we tested a patch which consisted of 211 .jsp files,a DB
script for creating 3 tables and 103 .class files. The testing was not successful
as only 77 out of 211 .jsp files were deployed,3 tables were created and none of
the .class files were deployed
RA Team Response was that the flow went to an unstable state and the issue was
unique.

As there were issues with large scale deployment and also the depoyment rate was
not good we did a 2nd round of testing with only 13 .class and 13 .jsp files and a
DB Script to create 3 tables.This time all of them got deployed but the Rollback
process failed.
The Response of the RA Team was that the Rollback path was not correct.

After correcting the Rollback path we went ahead with 3rd round of testing. This
time also all 13 .jsp/13 .class files were deployed along with the creation of the
3 tables. But in the Rollback process only the .jsp files were rolled back,
rollback of the class files failed.

After rectifying the flow, 4th round of testing took place. This time the patch
contained 25 .jsp/ 25 .class files an a DB script to create 3 tables. None of
the .jsp/.class files were deployed but the 3 tables were created.
RA Team response was that the .jsp/.class files got deleted somehow while doing tar
thus the .tar file uploaded in the SVN didn't contained any .jsp/.clas file.