Apache Jmeter has six successful releases with a time gap of two years only. With every release we can see a lot of new features, enhancements, Non-Functional Changes and Bug fixes. This shows a continuous involvement of community to enhance the product to its best.
Lets pick some of the good features added to Jmeter2.11:
1) Summariser in Non GUI mode:
In Previous versions of Jmeter you need to add a listener named Generate Summary Result to the jmx file. So that you can view the Summary in NON GUI mode after 3 minutes(180 sec) by default.
With 2.11 you can view the summary in non gui mode by default. You can also tweak the summary result by editing the following properties files.
# Summariser – Generate Summary Results – configuration (mainly applies to non-GUI mode)
# Define the following property to automatically start a summariser with that name
# (applies to non-GUI mode only)
# interval between summaries (in seconds) default 30 seconds
# Write messages to log file
# Write messages to System.out
By default summariser name would be “Summary”. You can edit and give a name of your own convenience. No Name means disabled summariser.
30Sec is the default interval which can be editable
If it is true then all the summariser information is going to be append to the Jmeter.log file. Changing it to false do not add any information of summariser.
Decides whether to show the summariser information to standard output.
You can view the command prompt as below.
2)Introduction of “Save as Test Fragment”
What is Test Fragment:
For a complex piece of Test Plan it is very tough to maintain, debug and execute the script. Code re-usability with a complex script is almost 0%. So it is always a best practice to split your test plan by functional components. Lets say for a banking application, you can create a jmx file for
1.login and logout
2.Account Summary & mini statement
So the main idea of Test Fragmentation is to split the complex test Script by functional components for better maintenance and code re-usability.
So with Jmeter2.11 you can select a group of element and save them as a test Fragment. Later just grab them and merge to which ever script you want using Include and Module Controller. I found it very time saving as it saves time and able to reuse the script/code efficiently.
3)Instant Xpath Tester:
I personally felt the RegExp Tester is a great help to test any regular expression before applying it to the script. Jmeter 2.11 has given one addition to it by featuring Xpath Tester. You can take any Xpath Expression and put it in the View Result Tree and test it if it is appropriate.