What is involved in testing the performance of both the client and the server in web testing

Relying on Tencent Security's accumulated experience and massive threat intelligence for many years, Tencent Yuzhi has built on the functions of enterprise asset detection, asset vulnerability analysis, vulnerability detection, tamper monitoring, availability monitoring, etc., and detects enterprise network risks through asset discovery, risk scanning, site monitoring and other aspects to meet the needs of visual management of assets and security information.

1. General indicators.

2. Web server metrics.

The average number of responses per second is the ratio of the total request time to the number of seconds. The average number of iterations of a business script per second. Successful requests and failed requests.

The number of successful clicks and the number of failed clicks. Clicks per second, successful clicks per second, and failed clicks per second. Number of connection attempts.

3. Database server indicators.

The number of user connections, that is, the number of connections to the database. The number of database deadlocks. Hits to the database cache.

Load testing: Increasing pressure on the system under test until the performance metrics reach their limits, the response time exceeds a predetermined target, or a resource is saturated. This kind of testing can find the processing limits of the system and provide a basis for system tuning.

Big data volume test: Tests large data volume for certain system storage, transmission, statistical query, and other services.

Configuration test: Find the optimal allocation principle of each resource in the system through testing.

Reliability test: You can apply pressure to maintain 70%-90% utilization of CPU resources, continuously pressurize the system for 8 hours, and then analyze whether the system is stable according to the results. That is, under the condition of loading a certain pressure, the system will run for a period of time.

Concurrent testing: to find some problems in algorithm design.

The performance test is mainly based on user concurrency testing.

Performance testing is primarily about finding software issues and hardware bottlenecks.

Answer] A

Whether the security mechanism and confidentiality measures of the detection system are perfect, mainly to test the prevention ability of the system; (3) Stress test: also known as strength test, it is a test of the bearing capacity of the pre-circular bibi system under abnormal conditions, and is to check whether the performance degradation is within the allowable range when the system is running in the limit state; (4) Performance test: check whether the system meets the performance requirements of the system design plan; (5) Functional test:

reliability testing, usability testing and maintainability testing; (6) Installation test: Client compatibility test. (7) Usability test: The user-friendliness of the test mainly depends on the final end of the system or the subjective opinion of the customer.

monitoring system fault tolerance; (2) Security test: to detect whether the security mechanism and confidentiality measures of the system are perfect, mainly to test the system's prevention ability; (3) Stress test: also known as strength test, which is a test of the system's ability to withstand abnormal conditions, and is to check whether the performance degradation is within the allowable range when the system is running in the extreme Xinwang state; (4) Performance test:

Check whether the system meets the performance requirements of the system design scheme specification; (5) Functional testing: reliability testing, usability testing and maintainability testing; (6) Installation test: Client compatibility test. (7) Usability Testing:

The user-friendliness of the test mainly depends on the subjective opinion of the end end of the system or the customer.

Since web applications are directly related to the user and often endure a large number of operations over a long period of time, the functionality and performance of the web project must be reliably verified. This is a false balance that has to be thoroughly tested by the web project. Web application testing is not much different from any other type of application testing.

Web performance testing involves a wide range of issues, but many web developers have encountered performance problems after the program is launched. This is usually manifested in the fact that the page speed starts to slow down dramatically, the normal access time becomes very long, or it simply throws you a bad luck error page. There are a lot of things that can happen here, but here are a few of the most important ones:

If the database connection exceeds the maximum limit, the connection pool of the program is full, and the connection to the database is denied.

Database deadlocks.

The web server exceeds the maximum number of connections (which is usually limited on virtual hosts) and memory leaks.

Too many HTTP connections, i.e., more access than the machine and software are designed to provide.

Configuration tests are used to test and validate software, running in different software and hardware configurations. Configuration testing is to test whether the software is compatible with other elements of the system that interact with it, such as browsers, operating systems, hardware, etc., to verify the performance of the software under test in different software and hardware configurations.

Web-based system testing is part of the configuration testing.

Server-side configuration test: If server-side configuration is allowed, then server-side configuration is performed. The purpose is to ensure that the server-side plan configuration can support the web application correctly;

Client configuration test: Ensure that the client is compatible with mainstream operating systems and browser software.

Web-based system testing mainly includes the following aspects:

Is the web application fully compatible with the server operating system?

When a web application is running, will system files, directories, and related system data be created correctly?

Do system security measures allow web applications to be executed without disrupting or degrading the user's service?

Can web applications be integrated with database software? Is the web application sensitive to different versions of database software?

Has the impact of a sysadmin error been tested on a web application?

Can a web application run on different operating systems? (Linux operating system, Windows, etc.).

Can I run a web application on different versions of the same operating system platform?

Does the web application work properly in the mainstream browser software on the market? (e.g. Firefox, Chrome, IE8, Google).

Are you asking the web project to test before installation on the system, or to test the system itself?