Contact Us

Our Services

Visual Reports of Performance Tests

An image representing visual reports of performance tests

Types of Performance Tests

Load Test

Simulates the number of virtual users that might use an application. In reproducing realistic usage and load conditions, based on response times, this test helps to identify potential bottlenecks. It also enables understanding the necessity to adjust the size of an application’s architecture.

Unit Test

Unit testing simulates the transactional activity; the goal being to isolate transactions that could disrupt the system as a whole.

Stress Test

Evaluates the behavior of systems nearing peak activity by increasing user load continuously.

Soak Test

This increases the number of concurrent users and monitors the behaviour of the system over a more extended period. The objective is to observe if intense and sustained activity over time shows a potential drop in performance levels, making excessive demands on the resources of the system.

Spike Test

Spike testing seeks to understand implications to the operation of systems when activity levels are above average. Unlike stress testing, spike testing accounts for the number of users and the complexity of actions performed (hence the increase in several business processes generated).
We provide visual reports of performance tests we conduct, this helps for easier understanding of the results so that actions can be put in place to improve application performance. Reports are typically very technically focused and detailed, we simplify this for the user given their specific role in the software development lifecycle.
NOTE: Visuals; there will be 4 or 5 sample reports/screenshots from previous tests conducted

What does performance testing measure?

  • Excessive Load Times

    This is the allotment required to start an application. Any delay should be as short as possible – a few seconds, at most, to offer the best possible user experience.

  • Poor Response Times

    This is what elapses between a user entering information into an application and the response to that action. Long response times significantly reduce the interest of users in the application.

  • Limited Scalability

    This represents a problem with the adaptability of an application to accommodate different numbers of users. For instance, the application performs well with just a few concurrent users but deteriorates as user numbers increase.

  • Bottlenecks

    These are obstructions in the system that decrease the overall performance of an application. They are usually caused by hardware problems or ineffective code.

Why performance test?

  • Regular Performance Testing

    Regular performance testing will help ensure your software meets the expected levels of service and provide a positive user experience.

  • Migrating to the Cloud

    Migrating to the Cloud? If you want to be assured that the performance of your critical applications are not degraded, you need us to performance test and benchmark them pre and post migration to the cloud!!

  • Improving Application Responsiveness

    Are your software applications slow and unresponsive to user demands? Get us in, we will help you improve the responsiveness of all your critical applications!

When to do performance test?

As early as possible and regularly as performance tests focus on components (web services, microservices, APIs). The earlier the components of an application are tested, the sooner any anomaly can be detected and reduces the time and cost to fix it. They should also be done regularly so that performance trending can be understood. If you are migrating critical applications to the cloud, it is highly recommended to benchmark performance pre and post migration in order to ensure performance continuity and assure a positive end user experience after the migration to the cloud.