Performance Test
Response times need to be continually measured and verified to ensure that response time requirements are met and expectations for your system are fulfilled. Validation must be performed not only in the context of normal, everyday use, but also under peak load conditions and to determine the system’s performance limits. Know your application and its risks.
Application response times can change when subjected to prolonged loads, due to filled queues and logs, memory leaks, etc. Unfortunately, these events often lead to users experiencing errors, or — in the worst case — a system failure. Lengthy and ongoing tests are essential to ensure stable operation and a positive user experience.
The system’s ability to scale is a key parameter in performance testing. Validating whether the current set-up and capacity are sufficient for production use is vital. It is equally important to understand the risks of a future scenario involving an increased load.
Our proven approach to performance testing ensures a rapid, cost-effective solution to solving the task.
The purpose of the pre-analysis is to identify areas of focus and get an overview of the performance test, identify the tasks ahead and plan, uncover risks and grey zones, and to analyse the testability of the application. We do all this to clarify the complexity of the task, and the tools and resources needed to execute it.
The result of the pre-analysis is a performance test plan that provides a clear overview: Furthermore an estimate of the cost for scripting and executing the planned test, as well as the hardware and software expenses in order to execute the tests are included.
Environments, tools, users, and test data are prepared based on the task listed in the performance test plan. Furthermore, the scripts necessary to simulate the test itself will be developed and prepared at this stage. The test will be executed in accordance with the plan, and feedback will be provided as needed in the agreed format.
The typical format is a combination of metrics with conclusions and recommendations. After the first execution, there will be an opportunity to adjust the application or infrastructure before executing another test to validate the effect of the adjustments made.
Let us take you by the hand and guide you through your performance testing.
Mobile Apps
Performance testing applications on mobile devices needs to be performed on a representative set of devices and configurations in order to reflect real-world use.
IoT
IoT devices and sensors are connected to the internet to share data. This requires that the underlying system is able to receive, process and send data continuously and rapidly.
Integrations
Systems are often integrated with or dependent upon other systems, either internally or externally. Calls to these integrations can affect system response times.
Websites
Website performance can be business-critical for companies, in terms of lost revenue, reputation and the customer experience in general.
Networks / Databases
Front-ends and applications rely on both networks and underlying databases. These elements can affect performance, so they require significant focus during testing.
Desktop applicationer
Desktop applications, which typically represent vital business processes, should be tested to guarantee effective workflows and user experiences.
When solving problems within performance testing, there are different tools we can use, depending on what is to be tested and for what purpose. We are happy to work with the tools our customers are already using, but we can also supply the right solution ourselves, if desired.
As part of the test, we typically need to examine how the application works behind the user interface. We use a range of tools to inspect networks, infrastructure, databases, etc. New Relic is one offering in this space, but the customer’s own solution may be preferable.
Contact us by phone at +45 44 979 979, via email at info@testhuset.dk, or through our contact form.
Content