Performance Testing – Schroders

Background

e-testing consultants were assigned to Schroders to carry out a performance test on a Global Fund Management system. The system, provided by a third party, was a business critical implementation, consisting of a core set of mainframe based, remote applications, interfacing with a local implementation of a Windows based workflow management system for different areas of the business. Performance testing was focussed on a local server specific to the project, incorporating 7 different sub systems. In addition to workflow, these applications also incorporated document scanning, customer relationship management, marketing, printing and overall reporting using Business Objects.

Workload

The first step was to document the key business processes that would be used in the live environment, for each application. Once this was done, the likely usage profile of each of the main applications was estimated, based on metrics already in existence at the company. Each of the applications was recorded using LoadRunner and the scripts modified, so that when running, each iteration would use different and life-like test data. The work done when specifying the transactions and the numbers of users was carried out in close conjunction with the users and project teams within the business. To this end, plans were circulated and presented to agreed review groups, to ensure that the scope of testing was agreed with all parties, up front.

Results

Once tested and verified as complete, the individual scripts were put together into a test scenario, to accurately simulate the likely peak working day within the company, once the system was up and running. Initial test iterations were then run on the complete system. The initial tests executed found the system lacking – it was supposed to have a working capacity of over 200 users. The first tests carried out failed before getting to the 25 user level. The tests were carried out repeatedly, to identify bottlenecks within the system. Numerous bottlenecks were identified on each iteration, including table indexes, record locking problems and over complex individual stored procedures. Once changes to problems had been implemented, the tests were then run again. 20 full test cycles were run until the system could be signed off as fully functional for the required number of users. Tests were completed to the timescales identified in the initial schedule put together by e-testing.

The use of e-testing’s services enabled Schroders to identify potentially damaging problems prior to going live with a business critical fund administration system. The ability to pinpoint defects quickly so they could be addressed by the development team and re-tested proved a significant factor, enabling Schroders to successfully implement a fully working system to schedule.