Installing Jmeter on ubuntu
Installing JMeterJMeter provides a GUI for test building, allowing you to create various elements in a tree to craft complex load tests that handle a wide variety of different scenariosInstallation is typically quite easy. On Ubuntu, you can install it with apt-get. $ sudo apt-get install jmeter or Download and install the JMeter Open Jmeter (bin/Jmeter.sh on Linux) Configuration : Add (via right click) a Thread group to the Test Plan Add a Non Test Element > HTTP Proxy Server to the Workbench Open the HTTP Proxy Server Page and change the port if required Set the Target Controller to Test Plan > Thread Group on the same page Configure your browser (Firefox!) to use the Proxy Server (it's localhost) Press Start at the bottom of the page Now, JMeter will record all the HTTP requests your browser makes,so make sure you have closed all the other tabs you have open, otherwise you will get a mixture of Ad's and ajax requests recorded as well. Basic understanding of Jmeter
Let us take a view at how a request for
web page is sent to the Web server from a User's browser, and how a
web page is finally displayed. Understanding this workflow will
give us opportunity to imagine how JMeter fits in this workflow and
how it can do same thing as a browser does.
Now introducing Apache JMeter into the
picture. The actions taken by the User are no longer required. The
User action trigger some HTTP requests which are recorded in a JMeter
HTTP Request Sampler for multiple uses.
See how JMetr replaces a browser, but
how the working is a little different.
So what makes one User transaction in
terms of JMeter?
When we add a HTTP Request Sampler in
JMeter Test plan it stores one Web Page calling and receiving
sequence. We can call this as a single user transaction. As
soon as we tell this to JMeter it is capable of doing the same thing
any number of times. It also does this multiple
times simultaneously.
As JMeter is not exactly a browser the
HTTP Request Sampler makes all the received data available for
further analysis. We use View Tree Listener for actually
visualizing the received response. View Tree Listener is a good
way to know what request was sent, what was the response and the
result of the transaction.
When JMeter simulates multiple users by
making the same call multiple times, in different operating system
threads (we can say execution paths) that time more analytical data
is available. The Summary Report Listener can show us the
additional calculated data line Minimum time and Maximum time taken
to receive the response. It also calculates the average time
taken using all the results together.
To use these items provided by JMeter
we will also need items like
For some advanced user transactions and
logical conditions there are Controllers. Once we learn how to
combine these elements we are ready to write our first Test Plan in
JMeter.
Yes initially this may seem like a lot
of jargon. Eventually we will get used to these elements and
then testing will be a piece of cake. Ok, let us re-visit what
they all mean in JMeter world.
We will write our first Test Plan step
by step in the next article but let us first get introduced formally
with the different elements we have seen till now.
 
Now we know some elements which will be
used in creation of a Test Plan in JMeter. It will be
worthwhile checking the difference between real world transactions
and the transactions that happen in JMeter world. Is there one
to one mapping between actions performed in real world and while
executing a JMeter test plan?
 Refer a video tutorialhttp://www.artemissoftware.net/display/art/JMeter+Quick+Start+Video+-+create+execute+analyze+in+less+than+5+minutes |
No comments:
Post a Comment