Microsoft Web application stress tool is a set of tools developed by Microsoft website testers to perform actual website stress testing. With this powerful stress testing tool, you can use a small number of client computers to simulate the potential impact of a large number of users going online on website services, before the website is launched, perform a test on the website you designed in the real environment to identify potential system problems and further adjust and set up the system.
Microsoft Web application stress has the following features:
* Test commands can be created in several different ways: includes manual, recording browser operation steps, or directly entering IIS record files, website content, and instructions for entering other test programs.
* Supports multiple client interfaces: The standard website application C ++ client, uses the Active Server Page client, or uses the web application stress object model to create your custom interface ..
* Multiple users can use different authentication methods to simulate the actual situation, including DPA, NTLM, and SSL.
* Supports dynamic cookie simulation to customize the actual website operation scenarios and sessions.
* The computer on the client performs the simulation in the form of an NT Service. You can delete the test computers on some clients without interrupting the test.
* By using a centralized Microsoft Web application stress administrator, you can use any number of client computers for testing at the same time.
* The bandwidth throttling function is provided to simulate the online use of the modem.
* The built-in query-string editor helps you create a name-value pair combination template and can be used repeatedly in tests in different scenarios.
* The programmable object mode allows you to create your own test client.
* A summary of test reports and a wealth of performance test materials.
* The Domain Name System (DNS) is supported to allow you to test machines in the entire cluster.
* Use the page group method to control the file group and the execution program of test commands.
* Customizable headers allow you to simulate different types of browsers.
* Customizable command latency allows you to test in a closer way to the real environment.
Website test Overview
To correctly use was for website stress testing, you need to have a preliminary understanding of the website testing method. The following discussions will cover some basic concepts for your reference.
The website test can be divided into three main categories:
* Performance Testing)
* Website stability (stability or stress testing) under stress testing)
* Website affordability evaluation (Capacity Planning)
The first job of website performance testing is to use testing tools to pressurize websites to measure the maximum number of requests per second that a website server can bear. The second task is to find out the cause of system performance restrictions. For example, the response latency caused by CPU, memory, or backend systems.
In many cases, the CPU of the website server is the main performance bottleneck. During the test, you can continue to pressurize until the performance starts to drop, and then slowly reduce the pressure. The maximum performance you have tested is the maximum performance that the website can achieve. During the actual test, you can increase the pressure thread or increase the client that executes the was test program to pressurize the program.
On the website server side, you can use performance monitoring tools such as performance monitor to monitor such as "system: % Total processor time" and "Web Service: connection attempts/sec "or" Active Server Pages: Requests queued "pointer. If the CPU resource pointer reaches 80% to 85%, the CPU processing capability is most likely the bottleneck of the entire system. If the CPU usage ratio is not high during stress testing, the "Requests queued" pointer remains high, it may be that the program is calling the COM component on the server and this component cannot effectively execute all the commands, thus reducing the system performance. In this case, the COM component on the server is the real bottleneck.
Currently, the most popular custom website applications on the market also have a significant impact on the performance of the website. Was includes several features that can effectively help you test custom website applications. For example, you can create a user so that was can set and store cookies for each user. You can also use the querystring editor to help you create and store several different name-Value Pair files for testing each time a request is executed.
General website Test Problems
* The error test platform is different from the actual production server, and the actual problem cannot be detected.
* Incorrect test commands cannot correctly simulate the real response of the online system.
* Thread security issues and unstable server COM components.
* Error in Active Server Page and Global. Asa settings.
: Http://www.microsoft.com/downloads/details.aspx? Familyid = e2c0585a-062a-439e-a67d-75a89aa36495 & displaylang = en
