Web test methods

Search function

If the query condition is an input box, refer to the test method of the corresponding type of the input box

1. Function Realization:

(1) If a fuzzy query is supported, search for any character in the name to find out

(2) Whether the long name can be found

(3) The matching condition does not exist in the input system

(4) When the user queries the operation, the general situation is not to clear the query conditions, unless the requirements of special instructions.

2. Combination test:

(1) Choose between different query criteria, whether there is a page error (Radio box and multi box is the most error prone)

(2) When testing multiple query conditions, we should pay attention to the combination test of the query conditions, possibly different combinations of tests will be error.

Performance Test 1. Connection Speed test:

The speed at which users connect to Web applications varies depending on how they surf the internet, and they may be telephone dialing or broadband access. When downloading a program, the user can wait a long time, but if you only visit a page it will not. If the response time of the web system is too long (for example, more than 5 seconds), the user will leave without patience.

In addition, some pages have a timeout limit, if the response is too slow, the user may not have time to browse the content, you need to re-login. Moreover, the connection speed is too slow, may also cause the data loss, causes the user to get the real page.

2. Load test:

Load tests are designed to measure the performance of a web system at a certain load level to ensure that the web system functions properly within the requirements range. The load level can be the number of users who have access to the Web system at any one time, or the amount of online data processing. For example: How many users can a Web application be allowed to be online at the same time? What happens if this quantity is exceeded? Can web applications handle a large number of users ' requests for the same page?

3. Stress test:

The load test should be scheduled to be tested in the actual network environment after the web system is published. Because a company's internal staff, especially the project team, is always limited, and a web system can process the number of requests at the same time far beyond this limit, so only on the Internet, accept load testing, the results are correct and trustworthy.
Stress testing refers to the actual destruction of a Web application system, the test system reflects. Stress testing is the ability to test system limitations and resiliency, which means that testing Web applications will crash and under what circumstances. Hackers often provide incorrect data loads until the Web application crashes and then gain access when the system restarts.
Areas of stress testing include forms, landing, and other information transfer pages.

Web test methods