As software testers, we often encounter stress testing, stability testing, functional testing, performance testing, compatibility testing, etc. Sometimes we use the points contained in these testing methods imperceptibly in our work, but we do not Too much care to summarize and sort out, then what is the focus of each test method? For example: What should we pay attention to most in the process of performance testing? Waiting for thoughts, after several summaries, today we will first sort out the focus of the performance test, and the rest of the test will be supplemented in the blog post.
Concept: a test to check whether the performance of the system meets the requirements
Performance is the most critical dimension for evaluating a software. Performance testing focuses on: how much and how fast
1. Classification of performance test:
1) Limit test:
Under various boundary pressure conditions, such as battery, storage, network speed, verify whether the APP can respond correctly, install the APP when the memory is full—the phone is powered off when the APP is running—the network is disconnected when the APP is running
2) Response ability test:
Whether the various operations in the APP meet the user's response time requirements, APP installation-APP uninstall-the response time of various functional operations of the APP
3) Stress test:
Occupation of system resources under repeated/long-term operation
2. Performance evaluation:
Evaluate the usage of system resources in typical user application scenarios (testable aspects: installation and startup time—CPU usage—memory usage—traffic consumption—power consumption—network speed—backend (number of concurrent connections) ), test whether various operations in the APP meet the user response time requirements)
Three, performance test indicators:
The source of the performance test indicators: the user's clear requirements for each indicator, if the user does not provide performance indicators, design the indicators according to the user needs and the experience of the test designer (requirements + experience)
-
1) Availability (available time)
-
2) Response time (the time it takes for the user to initiate a request to when the application responds to the user's client)
-
3) Throughput rate (probability of occurrence of certain application-oriented time)
-
4) Resource utilization (percentage of the theoretical capacity of a certain resource)
Fourth, the purpose of performance testing:
-
1) Performance indicators of the test system
-
2) Check the performance bottleneck of the system
-
3) Give a more appropriate software and hardware configuration plan
-
4) Check whether the hardware configuration can meet customer needs
Ultimately play the purpose of optimizing the system
The following is some sorting and collection that I also made, I integrated these resources into a warehouse,
For software testing friends, it should be the most comprehensive and complete interview preparation warehouse. In order to better organize each module, I also refer to many high-quality blog posts and projects on the Internet, and strive not to miss every knowledge point. Friends relied on these contents to review, and got offers from big factories such as BATJ. This warehouse has also helped many software test learners, and I hope it can also help you.
Pay attention to the official account: Programmer Erhei, you can get a complete set of software testing resource collection warehouse