Performance Testing

Performance Testing

Why Performance Testing?

The capacity to respond quickly, to handle a large number of simultaneous users, and to remain stable under different loads defines the level of product performance. It influences user experience and company reputation.

QATestLab carries out performance testing to objectively assess system operation speed, scalability, and stability. We verify whether the system is able to withstand high loads of different volumes, duration, and velocity of change based on its technical requirements.

By conducting performance tests, we do not detect bugs, we find system performance bottlenecks before release to market.

By thinking outside the box, we design and execute atypical testing scenarios for products and solutions to cope with days such as Black Friday when traffic is very high. Even if the system is under development for a couple of years and functions properly without serious bugs, it does not mean that it will be able to withstand high traffic and increased data processing during, for example, New Year’s Eve.

What We Do

  • Load testing to detect performance issues under heavy loads of traffic and data processing
  • Stress testing to check system behavior under higher than expected traffic and data processing loads
  • Endurance testing to verify the system capacities to handle a certain load over a long period of time
  • Spike testing to monitor the system behavior in the event of sudden spikes
  • Volume testing to check the system with different database volumes
  • Scalability testing to verify the system capacity to handle the planned load increase

When conducting different types of performance testing, we evaluate system capacities of different software products - simple web and mobile applications, lightweight HTML websites, heavy systems with JavaScript code, REST API services, etc.

Bugs We Find

  • Long load time
  • Performance bottlenecking - CPU/memory /network usage, OS limitations, etc.
  • Poor scalability
  • Long response time

How We Test

performance testing process

What We Need to Start

  • Access to the testing environment of the application
  • Statistics on average amount and duration of user sessions per day/week, response time under average and peak loads
  • User scenarios to be used in scripts
  • Particular objectives of checking

Tools We Use

tools 
More than 500 virtual users LoadRunner
Less than 500 virtual users JMeter
API running SoapUI test suites LoadUI
Work of UI under additional load Selenium scripts
Additional customer’s requirements Assertions added for JMeter, SoapUI and SLI in LoadRunner scripts

Ensure Positive User Experience Even During a High Workload

performance testing 

By thinking outside the box, we design and execute untypical testing scenarios for products and solutions to withstand all Black Fridays when the traffic is very high. If the system is under development for a couple of years and functions properly without serious bugs, it does not mean that it will be able to carry large traffic and high data processing during, for example, New Year’s Eve.

To avoid sudden “Black Friday” crashes and system malfunctions, we conduct several types of performance testing. When designing testing scripts, we always focus on the end-user, not server capacities, and take into account previous user experience in order to detect performance bottlenecks in the system and ensure flawless activities. test123