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
2,280 total views, 1 views today
The MVA offers excellent resources (videos, decks with author notes etc.,) on a variety of technologies offered under the Microsoft space, all at free of cost for the benefit of IT Engineers and developers.
1,007 total views, no 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
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
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
NInject as a DI framework helps to deal with the common scenario of avoiding creation of concrete objects by providing the basic infrastructure to inject the required objects (using Constructor Injection technique).
Use of Composition Root Pattern: Composition Root is a pattern where the “object graph” definitions are handled in a centralized area. For instance in the case of an ASP.NET MVC (that uses NInject.MVC3) application, the RegisterServices(Ikernel kernel) is considered as the entry point for the application where all dependencies are defined by binding the respective interfaces to the concrete objects (using the Bind API).
Hence by way of maintaining the construction of objects in a single location, the core components will live independent of any dependencies and the DI framework will inject the required interfaces, on-demand.
622 total views, no views today
This post is in continuation to the earlier post on NInject and assumes that the reader has knowledge about NInject and DI concepts. For those, who stumbled upon this link accidentally, read my previous blog about using NInject with ASP.NET MVC4 to get a better idea about NInject.
NInject 3.0 offers a fluent syntax that helps to bind multiple interfaces with a concrete implementation.
2,395 total views, no views today