9 Limitations and Assumptions

Support from the developers/business analysts for business transaction review fo

r the list of transactions identified.
Performance test is to be conducted in the CATE test environment.
A functionally stable Post-GU application (equivalent to the one used for script
ing at offshore on which test scripts were created) should be deployed in the CA
TE environment.
Environment and Data setup as per the Test Plan for the transactions to be teste
d will be done with the support of a coordinator at onsite/offshore.
All tests will be conducted with a volume base as equivalent as that of the prod
uction database set up.
Testing tool Load Runner 7.51 will be made available for the E-Test lab team at
onsite for execution.
Machines for the E-Test team to deploy in built Data extraction tools for data c
orrelation and analysis will be provided.
Access to the servers will be provided to E-Test team to monitor various layers
of the application test environment.
During Test execution, services that are not related to the Post-GU should be st
opped to isolate the test environment for Post-GU application.
onsite support for Data collection from various layers.
onsite support for analysis if any bottleneck identified at the application leve
l.
Batch Jobs scheduled when is online in the Production environment can be simulat
ed in CATE-environment.
Hardware bottlenecks if any will be identified and reported. Tests should be per
formed only on vertical/horizontal scalable hardware to confirm the resolution o
f the same and no recommendations on extrapolation of results will be provided.
SQL statement will be reviewed and tuned if there is degradation in response tim
e.
If the response times of any component method call within the scope of the ident
ified transactions are unacceptable then they will be analyzed and suggestions t
o improve the same will be given as part of the Executive summary report.