e-testing were invited to assist in offering guidance on test approach and process, in order to better prepare the IT department to validate software releases as they were delivered.
The health check identified areas for
improvement and was able to pinpoint a set of prioritised recommendations,
which were quickly put in place.
An e-testing test manager was promptly deployed to manage the test programme, with initial responsibility for System Integration Testing.
Working with the internal team, the test manager developed a test plan, based on requirements – which was signed off by the project team before additional e-testing consultants joined the project to develop test scripts for an initial cycle of integration testing against the delivered system.
We worked closely with the offshore developers to triage and prioritise defects for fixing via TFS, which were re-tested before regression testing the system as a whole.
Planning commenced on a parallel phase of performance testing and we soon deployed a principal performance specialist on the project.
He had to carry out planning and manage the phase, followed by performance specialists to script the identified user journeys and create the scenarios in HP LoadRunner.
Due to the high degree of security
implemented in the communications, it was necessary to drive virtual users via
real browsers, thus necessitating a significantly higher level of client-side
system resources to drive the tests – in particular CPU and RAM.
HP StormRunner Load was used to drive the
tests via the Cloud, using the flexible HP platform for deploying tests and
injecting load, via HP server farms.
Several cycles of testing were then executed, which picked up a number of problems in a number of areas, including some UI elements, as well as at the database layer. As problems were rectified, tests were re-run, performing a tuning exercise on the infrastructure, and the application itself.
