Create a Load Test project using Visual Studio 2013 – Part 6

In this post, let’s create a “Load Test” artifact, to test against the ASP.NET MVC sample application (created in the previous post – Creating a sample ASP.NET MVC application for Web Performance Testing – Part 2).  Before proceeding, make sure that you have created a new “Web Performance and Load Test Project” by following the steps outlined in this post (Creating a New “Web Performance and Load Testing Project” – Part 3.)

Continue reading

7,889 total views, 6 views today

Creating “Reusable” Tests / Parts in WebTest (using Visual Studio 2013 Web Performance and Load Testing project) – Part 5

Reusable” Components/Parts in software development practice had always been the suggested approach to reduce the time taken to build applications and help reduce the overall duration to market it.

The same concept is applicable even in the case of “Load Testing” where often, large applications are broken into parts for rolling out Load Tests on targeted features/sections of the application to obtain more insights on the behavior of those “critical” sections of the application during load testing.

Continue reading

2,952 total views, 2 views today

Additional properties to be configured for “Web Performance Test Editor (WebTest)” for Visual Studio 2013 – Part 4

In the previous post, we looked at recording a new test and in this post will explain some of the most important configuration settings options, provided by the Web Performance Test Editor that can help enhance the load testing capabilities, to get better information/ statistics, when running load tests on real-world web sites.

Continue reading

3,936 total views, 4 views today

Creating a sample ASP.NET MVC application for Web Performance Testing – Part 2

Introduction

In this blog let’s create a sample MVC web application to be used for load testing using the “Web and Performance Testing” project in Visual Studio. This step is not mandatory as you can very well use any website to record your test against (though I would advise trying against sites such as Google or Yahoo, which can sense such testing and perceive them as Denial of Service attacks, which in turn would lead to blacklisting of your outgoing IP and would force you to enter a CAPTCHA every time you try Google or Yahoo, then after).So, it’s better to create our own simple application which can be always extended to accommodate some of the advanced concepts which require mimicking real-world scenarios.

Continue reading

2,913 total views, 5 views today