Performance testing is an important part of software testing. Its purpose is to evaluate the performance of the system under different loads, including response time, throughput, concurrency and other indicators. Performance testing can usually be carried out through the following methods:
1. Load test
Load testing is to simulate multiple users accessing the system at the same time to test the performance of the system under high concurrency and large traffic conditions. Load testing can be done using open source and commercial load testing tools such as Apache JMeter or LoadRunner. These tools can simulate virtual users and monitor system performance metrics such as response time, throughput, error rate, etc. The specific sample code is as follows:
// 导入jmeter相关的类库
import org.apache.jmeter.control.LoopController;
import org.apache.jmeter.engine.StandardJMeterEngine;
import org.apache.jmeter.protocol.http.sampler.HTTPSampler;
import org.apache.jmeter.reporters.ResultCollector;
import org.apache.jmeter.testelement.TestElement;
import org.apache.jmeter.testelement.TestPlan;
import org.apache.jmeter.threads.SetupThreadGroup;
import org.apache.jmeter.util.JMeterUtils;
public class LoadTest{
public static void main(String[] args) throws Exception{
// 初始化JMeter引擎
StandardJMeterEngine jmeter = new StandardJMeterEngine();
JMeterUtils.setJMeterHome("/path/to/jmeter");
JMeterUtils.loadJMeterProperties("/path/to/jmeter/bin/jmeter.properties");
// 创建HTTP请求
HTTPSampler httpSampler = new HTTPSampler();
httpSampler.setDomain("www.example.com");
httpSampler.setPort(80);
httpSampler.setPath("/api/v1/login");
httpSampler.setMethod("POST");
// 创建测试计划
TestPlan testPlan = new TestPlan("Login Test Plan");
testPlan.addThreadGroup(new SetupThreadGroup());
LoopController loopCtrl = new LoopController();
loopCtrl.setLoops(100);
testPlan.getThreadGroups().get(0).setSamplerController(loopCtrl);
// 添加监听器
ResultCollector resultCollector = new ResultCollector();
testPlan.addTestElement(resultCollector);
// 运行测试计划
jmeter.configure(testPlan);
jmeter.run();
}
}The above code uses the Apache JMeter library to simulate 100 users accessing the login interface and records performance indicators.
At the same time, I have also prepared a software testing video tutorial for everyone (including interviews, interfaces, automation, performance testing, etc.), which is below. If you need it, you can watch it directly, or you can directly click on the small card at the end of the article to get the information document for free.
Where to watch software testing video tutorials:
Byte boss teaches you how to master automated testing (interface automation/APP automation/Web automation/performance testing) within 15 days, including practical project practice
2. Stress test
Stress testing is a continuous test of the system's ultimate endurance by gradually increasing the load. Stress testing can be performed using open source and commercial stress testing tools such as StressTest or LoadUI. These tools can continuously make requests and monitor system performance metrics such as response time, throughput, error rate, etc. The specific sample code is as follows:
import time
import requests
def stress_test():
url = "http://www.example.com/api/v1/login"
data = {"username": "testuser"}
count = 0
start_time = time.time()
# 持续发出请求，直到达到最大负载量
while (time.time() - start_time) < 60:
response = requests.post(url, data)
if response.status_code == 200 and response.json().get("result") == "success":
count += 1
# 输出性能指标
print("Total requests: {}".format(count))
print("Requests per second: {:.2f}".format(count / 60))The above code simulates continuing to make HTTP requests until the maximum load is reached. In this example, the maximum load is set to 60 seconds.
3. Concurrency testing
Concurrency testing is to test the performance of the system when processing multiple requests at the same time. Concurrency testing can be done using open source and commercial concurrency testing tools such as Gatling or LoadStorm. These tools can simulate multi-thread, multi-process scenarios and monitor system performance indicators, such as response time, throughput, error rate, etc. The specific sample code is as follows
import io.gatling.core.Predef._
import io.gatling.http.Predef._
import scala.concurrent.duration._
class ConcurrentTest extends Simulation {
val httpProtocol = http
.baseUrl("http://www.example.com")
val scn = scenario("Concurrent Test")
.exec(http("Login API")
.post("/api/v1/login")
.formParam("username", "testuser")
.formParam
setUp(
scn.inject(
constantUsersPerSec(10) during (30 seconds)
)
).protocols(httpProtocol)
}The above code uses the Gatling library to simulate 10 users concurrently accessing the login interface for a duration of 30 seconds, and records performance indicators.
4. Configuration test
Configuration testing is to test the impact of modifications to the system configuration on system performance. You can manually modify the system configuration parameters and perform performance testing to verify whether the modified configuration optimizes system performance. The specific sample code is omitted.
5. Power outage recovery test and reliability test
These two tests need to be performed in the actual production environment and cannot be simulated through code. Monitoring tools, such as zabbix, can usually be set up in the production environment to continuously monitor the performance indicators of the system and perform analysis and optimization.
In short, when conducting performance testing, it is necessary to select appropriate testing methods and tools according to the actual situation, and conduct testing in conjunction with business scenarios. At the same time, the test results need to be analyzed and optimized to improve the performance and stability of the system.
A little help
PS: Here is a collection of self-study tutorials for software testing. It should be very helpful for those who are developing in the testing industry. In addition to basic introductory resources, bloggers also collect a lot of advanced automation resources. From theory to practice, only by integrating knowledge and action can you truly master it. The full set of content has been packaged on the network disk, and the total content is close to 500 G.
☑ 240 episodes - a complete set of video courses from zero to mastery
☑ [Courseware + Source Code] - complete supporting tutorials
☑ 18 sets - source code of practical testing projects
☑ 37 sets - testing tool software package
☑ 268 - real interview questions
☑ 200 templates - Interview resume template, test plan template, software test report template, test analysis template, test plan template, performance test report, performance test report, performance test script case template (complete information)
These materials should be the most comprehensive and complete preparation warehouse for friends who do [software testing]. This warehouse has also accompanied me through the most difficult journey. I hope it can also help you! Everything must be done early, especially in the technical industry, where technical skills must be improved.
