Application load and performance testing

Question

Dear all Good Afternoon. How can i perform some application load and performance testing ? is there any particular metthodologies too follow. I dont want to use any third party tools for this purpose. Just want to know about the underline methodologies. If anyone of you share the idea (any tutorial,lecture materials) that will be greatly appreciable. Kind regards Shayer

Tanvir Huda · Answer

Hello Spqilmore Thanks for your reply. I found few tools for testing. If anyone is interested please read the following articles/books that will be helpful to you in understanding the application load and performance testing. http://www.c-sharpcorner.com/Code/2002/Sept/AppTestCenter.asp http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag/html/scalenetchapt16.asp Apache JMeter is a free opensource tool that is used for application testing as well http://jakarta.apache.org/jmeter/usermanual/index.html Regards Shayer

spgilmore · Answer

There are two goals in performance testing. One is to find out how many operations per second the application can perform, and another is to find which part of an operation takes the most time. To find which part of an operation takes the most time, the proper way is to use a profiler. I know that you're not interested in third-party tools, but this is the standard practice. The only one I've used for .NET is OptimizeIt Profiler. The other purpose is to stress test your application, or to find out how many operations it can perform. You usually have to either build an application for that, or to build a framework that will exercise it. At my work we have GUI apps, which are not easily tested. But we designed the programs so that the GUI is separate from the logic, so we can test the logic programmatically without the GUI. We would normally write a framework for this that is very similar to unit testing such as NUnit (which is free). However, we were also using NUnit, so we decided to write a small layer on top of NUnit to do stress testing instead of unit testing and it does all the work for us. We just set up a class that calls our program code and the framework measures how long it takes, and checks the code for bugs at the same time. You have to be careful not to use fixture or to write your framework to not include fixture in its measurements or your measurements will be skewed.