Okey, first we can name our test plan, which by default is simply “Test Plan”. Let’s now look at the Test Plan options that we can configure.
The numbers to the left of the square are the number of active and the number of total number of threads. If the square had been green, it would mean that the JMeter is running. In the above picture we can see that the square isn’t colored, which indicates that the JMeter was not running at the time the picture was taken. The square notifies us whether the JMeter is running or not. On the right side of the picture there are some numbers and a little square. Notice the green play icon in the above picture it’s a Start button. To run the test plan, we could click the Menu – Run – Start or a green play icon in the toolbar menu those two are equivalent. Here we must also mention that we don’t necessarily have to save a whole Test Plan, but can also save a subset of a test plan, which can prove useful if we only want to save a specific element we would like to later import into all test plans. This is shown in the picture below:Īlternatively we could do the same thing by right-clicking on the “Test Plan” and selecting “Save Selection As” and save the Test Plan. To do that, we must click on Menu – File – Save Test Plan as and save it. The first thing we should do when defining a Test Plan is to save it to some file, so we don’t lose the already configured options later. There are a number of element groups, which we’ll describe later. To add elements to a Test Plan we must right-click on the “Test Plan” and choose “Add” for a menu of elements to become available. But some of the elements are mandatory and must be used regardless of the testing server. If we’ll test a HTTP server we must add different elements than if we’re going to test a LDAP server. To add appropriate elements we must first know what we would like to test. When the JMeter is loaded it can’t do anything by default, because there are no test elements added to the test plan the test plan is empty. There are various elements that can be added into the test plan, each of which is responsible for certain aspects of the test process. When we start JMeter, its user interface will look like the picture below:Ī test plan in JMeter specifies the steps the JMeter will test when it is run. The /lib directory contains utility jars, whereas the /lib/ext directory contains JMeter components and add-ons. This works because JMeter automatically searches for classes in the /lib and /lib/ext directories. apache-jmeter-2.7/lib/ext/Īfter that we just need to restart the JMeter and the jmeter-plugins should be loaded just fine. # mv JMeterPlugins-0.5.3.zip JMeterPlugins/ After downloading and installing the jmeter-plugins package, new entries will appear in the graphical user interface menu in JMeter.Īfter downloading the JMeterPlugins, we need to extract it: Most of them (but not all) can be found on the jmeter-plugins web site. Besides those, JMeter also has a lot of plug-ins that can be used to test the performance of other services implementing other protocols not described above.
0 kommentar(er)
