These posts cover various items about how Visual Studio Web and Load Testing features work, common questions about what settings to use, where and when to put forth extra effort and why different behaviors may be important to consider.
Within Visual Studio’s Loadtesting Framework there are a few different Load Profile models. I usually use only two of them. This post explains how each behaves.
This post shows how the Visual Studio Loadtesting framework handles the warmup and cooldown settings and what test items get reported when using these settings.
Learn how a Visual Studio load test that contains web tests attempts to simulate the caching behavior of the browser, and how this can be used to tune your web site.
What is an “Off-box request” and how are my test results impacted by including or excluding these off-box calls? Also, how can I control whether these calls are made?
Should you use think times between web calls? This topic is controversial, but it’s possible to determine which way is better, as long as you consider these examples.
“What is the best way to take the results from our tests with a small load and estimate how the system will behave under a full load?” Here are some thoughts on that.
This question is one of the few that has a wide range of answers. The most common is “It depends!”, but even when you get a concrete value, your mileage may vary.
This example shows how I approach calculating the workload and load pattern when using a mixture of real world historical data and the need to project future data
How can you emulate all of the clients in order to really see the full picture? Actually you should be asking “Do I really need to emulate all of the clients?”
When trying to simulate your environment, there are some things that you just cannot properly replicate. This post talks about local environment vs. the Internet