How We Work:

An Overview of a Typical Performance Testing Engagement

Our process is straightforward and has been developed from our experiences with many customers.

We start with an initial contact with our clients where we learn as much as we can about our customers' requirements, the technical architecture and the performance volumetrics.

Our Process

Our process is straightforward and has been developed from our experiences with many customers.
We start with an initial contact with you, the client, where we learn as much as we can about your requirements, the technical architecture and the performance testing volumetrics.
We also like to discuss our requirements, such as access to a suitable test environment, creation of a sufficient number of test users and access to appropriate staff to assist with script design, system monitoring and tuning.

We usually suggest that a proof of concept is performed to verify that the proposed testing tool solution is suitable. The chosen tool is dependent on the percieved complexity of your application. This process step typically lasts half a day and is free of charge.

We will produce a draft testing strategy document. This document may take several discussion and review iterations before it becomes the agreed Testing Strategy Document. This will be a comprehensive strategy that details the work to be carried out during the Performance Testing Engagement, it will detail the deliverables, costs and timescales.

At this stage we engage with you, the customer, in most cases agreeing a fixed price for the performance testing engagement.  The Strategy Document is chargeable but the charge will be waived if you engage with us.

The Next Step

The next step is to get the scripts developed; typically this takes a two - three days per script depending on the complexity of the transactions being scripted.

Once the scripts are created the test scenarios can be developed. It may be that only one scenario is required, most likely however is that a number of scenarios are required. These scenarios may need to be modified during the testing process as issues are uncovered and resolved which may cause the testing focus to change. The scenario brings together the automated scripts with the virtual users that will create the workload against your application.

Now on with the testing! Our experiences suggest that the test execution, test analysis and issue resolution phases are an iterative process. A period of testing is followed by a period of analysis then issue resolution followed by more testing. This approach is aimed at identifying and driving out the major issues first, then on to the next issue. Some applications perform perfectly first time and do not require this iterative process - some but not many!
A further period of more thorough analysis then takes place where a clear picture of the applications performance is determined. The result of this analysis forms the input to the reporting stage.

Our final step is to write a report which details the testing activities, the results that we found, our conclusions and any recommendations. The report will contain all the evidence that was gathered and a detailed breakdown of our conclusions and recommendations.
We are a Testing Consultantcy and can help you meet your requirements

Error: Only up to 6 modules are supported in this layout. If you need more add your own layout.