Web based applications are required to exhibit high performance levels, interactivity, security, and speed. Interoperability of applications across various platforms, browsers, servers and languages is critical. Further, increased customer usage means that these applications have to be user-friendly and simple while rising instances of Internet fraud demands that these systems are protected from unauthenticated/unauthorized users.
The importance of web based services in supplementing traditional business practices cannot be overstated. This, combined with the inherent risks associated with the Internet, dictates that web based applications are rigorously tested. Only an experienced domain focused independent testing team can understand the unique challenges involved in validating web based applications.
At Thinksoft, we have extensive experience in successful testing web based applications including Arimor SSl, Collateral Monitoring System, Indus Collection System, and e-Orion releases across domains such as Private Banking, Credit Cards, Investment Banking, Retail Banking, Core Banking, Lending Systems, and Corporate Banking.
The test was done for concurrent login user traffic and ramp up login user traffic (from 200 users to 1000 users) to ascertain bottlenecks in performance. The load test was carried out in order to find out the response time for each page to be displayed and also the overall time taken for the entire process from login to logout. We used HP Mercury Load Runner tool to validate the response time for the login, banner, home and logout pages of the application.
We conducted load testing in both development and User Acceptance Testing (UAT) environments. Code and architectural changes to improve the performance of the application were done by the developer based on the results of the load testing done by us.
The tests were conducted from the client's office in Chennai, India, by accessing their application server located in Germany. The client derived the following benefits from their association with us:
Significantly, we identified a bug in Mercury Load Runner V6.5, which was resolved by Mercury by switching over to V7.02.