Mirroring the Production Environment
The performance test environment should be as close to the production environment as possible. This includes the server capacity and configuration, network environment, the Web
If production equivalent hardware is not
Putting It Together in a Performance Test Plan
The performance test plan is a strategy or formal approach to allow everyone involved in a Web application, from the development team, test team, and management team, to understand exactly how, why, and what part of the application is being performance
This gives a brief description of the business purpose of the Web application. This may include some marketing data
This depicts the hardware and software used for the performance test environment, and will include any deviations from the production environment. For example, document it if you have a Web cluster of four Web servers in the production environment, but only two Web servers in your performance test environment.
This section illustrates what you are trying to accomplish by performance testing your Web application. Examples include identifying what throughput and concurrent usage levels you will be striving for as well as the maximum acceptable response times.
This will include a description of your user scenarios, tools you use to stress test, and any intricacies you will put in your stress scripts. This section will also explain what ratios and sleep times or
The scripts are
Performance testing is a critical phase of any Web application s development cycle and needs to be the critical
Stress Testing with Microsoft Application Center Test (ACT)
The purpose of stress testing is to identify and isolate Web application performance bottlenecks under load. Decreasing or eliminating these bottlenecks allows you to meet or exceed anticipated traffic requirements. After you have identified bottlenecks, you can tune the Web application and server to help minimize end user response times and ultimately provide a better