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
“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.
2,952 total views, 2 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
The new Visual Studio 2013 comes packed with a “Web Performance and Load Test Project” to perform load testing on websites which earlier required installation of specialized tools (such as LoadRunner for high end major projects, or use of Apache Bench, httpperf, OpenLoad etc., that can be used for targeted load testing against small projects). The new “Web Performance Test” available in Visual Studio 2013 can be compared to the “stelwarts” such as LoadRunner (except for the flexiblility in terms of supporting a wide variety of scripting languages), but it does offer some cool features that are worth considering, especially the huge cost associated with the “virtual user” licensing adopted by “LoadRunner”.
2,993 total views, 2 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