Mobile web performance testing essentials




Performance test

1. Connection speed test The speed at which

users connect to the Web application system varies according to the way they surf the Internet, they may be dial-up telephones, or broadband Internet access. When downloading a program, the user can wait a long time, but not if only visiting a page. If the web system takes too long to respond (for example, more than 5 seconds), the user will be impatient and leave.

In addition, some pages have timeout restrictions. If the response speed is too slow, users may not have time to browse the content and need to log in again. Moreover, the connection speed is too slow, it may also cause data loss, and users cannot get the real page.

2. Load testing

Load testing is to measure the performance of the Web system at a certain load level to ensure that the Web system can work normally within the range of requirements. The load level can be the number of users accessing the Web system at the same time, or the number of online data processing. For example: How many users can the Web application system allow online at the same time? What happens if this number is exceeded? Can a web application system handle a large number of user requests for the same page?

3. Stress testing

Load testing should be arranged in the actual network environment after the Web system is released. Because an enterprise's internal staff, especially the project team staff are always limited, and the number of requests that a Web system can handle at the same time will far exceed this limit. Therefore, only when it is placed on the Internet and receives a load test, the result is correct and credible.

Stress testing refers to actually destroying a web application system and testing the response of the system. Stress testing is to test the limitations and fault recovery capabilities of the system, that is, to test whether the Web application system will crash, and under what circumstances will it crash. Hackers often provide the wrong data payload until the web application crashes, and then gains access when the system restarts.

Areas of stress testing include forms, login and other information transfer pages, etc.

The test needs to verify whether the system can respond to a large number of users at the same time without being able to respond when users transmit large amounts of data, and whether the system can run for a long time. Accessibility is extremely important to users. If users get a "system busy" message, they may give up and turn to a competitor. The system detection is not only to use the normal access to the site, in many cases, there may be hackers trying to attack the server by sending a large number of data packets. For safety reasons, testers should know what to do when the system is overloaded, rather than simply boosting system performance.

Instant access spikes

If your site is used to publish lottery draw results, it's a good idea to have the system respond to millions of requests within a period of time after the winning numbers are published. The load testing tool can simulate N users accessing the test site at the same time.

Each user transmits a lot of data Most users of an

online bookstore may only order 1-5 books, but a college bookstore may order 5,000 textbooks on introductory psychology, the latter a grandmother buying Christmas gifts for her 50 children and grandchildren (indifferently Each child has their own email address) Can the system handle large amounts of data from a single user?

Long-term use

If site is used to process flower orders, expect it to run continuously for at least the week leading up to Mother's Day. If the site provides a Web-based email service, it is best to keep the site running for months, or even years. It may be necessary to use automated testing tools to accomplish this type of testing as it is difficult to do these tests by hand. You can imagine organizing 100 people to click on a site at the same time. But what about organizing 100,000 people at the same time. Often, when a test tool is used a second time, the benefits it creates are enough to cover the cost. Moreover, once the test tool is installed, it is only a few clicks away when you use it again.

TestBird

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=326165756&siteId=291194637