Wednesday, October 1, 2008

Integration Testing

InternetNews Realtime IT News - Apple Loses Bid to Dismiss iPhone Monopoly Suit
Earn Money Online! No Registration Fees. Guaranteed Payments.
http://www.moneycosmos.com/?r=364773

Instantly Turn your Computer into a Super TV. Enjoy iPod, PSP, IPhone, Movies, Music, MP3, TV Shows! - http://cbnk.biz/HLSTV364773RYRRGDK

Send SMS to India @ 1 Cent / SMS! Packs Start $2 Only - http://cbnk.biz/HL1CS364773RYRRGDK

Register (any name) .com website for 1 Year @ Rs.365 Only! Hurry! - http://cbnk.biz/HLDOM364773RYRRGDK

Win cash Rs.10,000. SMS BLUFF to 57333 (India Only) Free registration! - http://cbnk.biz/HLDDT364773RYRRGDK


 Quick Links:  GMail   Google Images   Google Maps   Orkut   Yahoo! Mail   Yahoo! Maps   Yahoo! Search   Live Search   Hotmail   Rediffmail  AOL  href="http://cnn.com/">CNN  SAAMA  Symantec  Genisys  Informatica  BusinessObjects 


Testing Types

Integration Testing
The objective of Integration Testing is to ensure that workflows are executed as scheduled with correct dependency.
Integration testing involves the following
1. To check for the execution of workflows at the following stages
Source to Staging A.
Staging A to Staging B.
Staging B to Core.
2. To check target tables are populated with correct number of records.
3. Performance of the schedule is recorded and analysis is performed
on the performance result.
4. To verify the dependencies among workflows between source to staging, staging to staging and staging to core is have been properly defined.
5. To Check for Error log messages in appropriate file.
6. To verify if the start jobs starts at pre-defined starting time. Example if the start time for first job has been configured to be at 10:00AM and the Control-M group has been ordered at 7AM, the first job would not start in Control-M until 10:00AM.
7. To check for restarting of Jobs in case of failures.
Technical Shakedown Test
Due to the complexity in integrating the various source systems and tools, there are expected to be several teething problems with the environments. A Technical Shakedown Test will be conducted prior to commencing System Testing, Stress & Performance, User Acceptance testing and Operational Readiness Test to ensure the following points are proven:
• Hardware is in place and has been configured correctly (including Informatica architecture, Source system connectivity and Business Objects).
• All software has been migrated to the testing environments correctly.
• All required connectivity between systems are in place.
• End-to-end transactions (both online and batch transactions) have been executed and do not fall over.





0 comments: