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.)
7,889 total views, 6 views today
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.
3,936 total views, 4 views today
In continuation to the previous post, we will look into the steps involved in creating a new “Web Performance and Load Testing” project.
(Note: Before you continue with the post, please make sure that you have downloaded and installed the Visual Studio 2013 Ultimate edition as the “Web Performance and Load Testing Project” is available only in Ultimate edition. You can download the Trial edition from this link – http://www.visualstudio.com/downloads/download-visual-studio-vs).
4,189 total views, 2 views today
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.
2,913 total views, 5 views today
Off late with the wide adoption of Nuget packages, it seems to be driving everyone crazy on how they can manage these packages by not storing them in the source control as they too often bloat the storage space with DLL’s, config files etc.,
So, the simple question is Will I be able to store only the code and configuration files to Source Control but let Visual Studio download Nuget packages automatically when trying to setup the source code on a new developer’s machine?
667 total views, no views today