In today’s highly-connected world, almost every organisation has a presence on the Internet. With an increasingly large proportion of interactions being performed online, and with many businesses relying solely on Internet-based revenue, a loss of this channel (for example a website crash) could be seriously harmful to the business. Sales could be lost both in the short-term due to system downtime, and in the long-term due to negative publicity and a loss of customer confidence that is hard to regain.
In addition, every medium-to-large sized organisation has business-critical internal systems that, if slowed or lost completely due to overload, could vastly reduce or even cripple the level of effectiveness of the organisation.
By far the most common cause of the scenarios above is that the system (or part of it) does not have the capacity to cope with the number of users that are accessing it. But how do you know that the hardware is powerful enough, and the software efficient enough, to provide the required level of service whilst being subjected to the expected level of load?
Performance Testing is the process of simulating these high levels of load in order to identify any bottlenecks in your system and ensure that it has the capacity to perform as expected at the current time and beyond.
- Analysis of your performance testing requirements to ensure you understand the key performance indicators
- Finding the best test tool for your application and budget
- Developing a performance testing strategy that fits your business
- Generating scenarios that will simulate realistic user activity
- Trouble shooting problems and analysing results
- Ongoing support or knowledge transfer/training for your team
The different kinds of performance testing offered by Testhouse are as follows:
Load testing is carried out in order to understand the behaviour of an application at a given level of load. This load can be the number of users expected to execute or number of transactions in a given time frame. Test results give us the response-times of all critical transactions. If the database and server are also monitored, this test can demonstrate potential bottleneck problems.
These tests are normally used to take the application to its functional limits, through its use by a far greater number of users than expected. Its aim is to determine the robustness of an application with an extreme load and helps administrators determine if the application will perform correctly in those circumstances.
The purpose of this test is to determine if the application can maintain loads continuously and for an extended period of time.
Testhouse understand that validating your applications performance doesn’t stop after go-live. However comprehensive your pre-live performance testing has been you can never completely replicate the live environment with real users. Testhouse can help you form a strategy for post-live monitoring of your application and help you find the best tools/services to support your requirements.
We work with a number of key partners and can provide a solution to cover areas including:
- Internal Network monitoring
- Active website monitoring
- Global End-user experience monitoring
- Data streaming monitoring