flag Chinese

Performance specific testing service

  • Home
  • Performance specific testing service

Performance specific testing

Software performance testing refers to using tools to simulate a large number of user operations to verify the load that a software system can withstand and identify potential performance bottlenecks; The timeliness and efficiency of testing function completion are generally tested using automated testing tools.

Performance specific testing objectives

When a new information system is launched or the business scale of the system expands, help the system's construction party (commissioning party) and users determine whether the system's performance can meet user needs. Testers use professional testing tools and techniques to help customers understand whether system performance can meet expected goals and verify the system's ability to run continuously. Performance testing is one of the important types of software testing that helps determine the performance of applications under workloads, such as responsiveness, scalability, reliability, speed, and stability. Performance testing is not helpful in detecting errors, but it can eliminate performance bottlenecks and improve the overall performance of the application.
  • 1.Helps evaluate software stability;
  • 2. Ensure performance defects are identified in the early stages of the development lifecycle;
  • 3. Help the team understand how applications run under normal load;
  • 4. Ensure to identify and eliminate differences;
  • 5. Help verify the functional characteristics of the application;

Performance specific testing related indicators

response time

The time it takes from the moment a request is initiated by the client to the moment the client receives a response returned from the server, typically measured in milliseconds.

Processing capacity (throughput)

The number of transactions processed by the system per second, measured in transactions per second. The higher the indicator, the better.

CPU utilization rate

Reflect the CPU utilization of backend servers, including user state, system state, wait state, and idle state.

Memory utilization rate

Reflecting the memory utilization of backend servers, a memory utilization rate of 99% does not necessarily indicate a performance bottleneck in memory. It is necessary to comprehensively analyze memory issues in conjunction with the memory usage of SWAP swap space.

Disk I/O

Reflect the disk read and write usage of the backend server, i.e. how many megabytes are read and written per second.

Network I/O

Reflect the disk read and write usage of the backend server, which refers to the number of megabytes of read and write transfers per second. Generally, it should not exceed 70% of the maximum transmission capacity of the device or link.

Performance testing scope

Benchmarking

When applying lower pressure to the system, check the operating status of the system and record relevant data as a basic reference.

Capacity testing

Construct records of different orders of magnitude in the database, run multiple business scenarios under a certain number of virtual users, and view the maximum number of online users that the system can process.

Stress testing

Gradually increasing the load causes the system resources to reach saturation or even failure, ultimately determining under what load conditions the system performance fails and obtaining the maximum service level provided by the system.

Load testing

Gradually pressurize to determine the processing capacity and various thresholds that the system can withstand, and determine the maximum load that the system can withstand while meeting system performance indicators.

Stability testing

By loading the system with certain business pressures (such as CPU usage at 70% to 90%), check if the system is running stably and if there are any memory leaks or other issues.

Recoverable testing

Test the disaster recovery and recovery capabilities of the system architecture through recoverable tests for load balancing, application clustering, database RAC, and other architectures.

Performance specific testing process

  • 1.Application evaluation: Submit performance testing requirements->Measurability assessment->Initial demand research->Workload assessment;
  • 2.Demand Plan: Testing requirement research->Test requirement analysis->Performance testing plan->Plan review;
  • 3.Test preparation: Environmental preparation->Script preparation->Performance data preparation->Performance scenario preparation;
  • 4. Scenario execution: Execute performance testing scenarios->Performance problem analysis and optimization->Regression verification of performance issues;
  • 5. Report Summary: Compilation and analysis of test results->Performance test report->Report Review->Test Summary->Provide a report to the client;