Scripting and Debugging Enhancements, Reporting improvements, New HTTP Request UI & HTTP Request Defaults, JSON Post Processor

1. JMeter 3
The New JMeter3 have lots of new feature, following are the major feature in JMeter3 :
1. New UI/UX
2. Scripting and Debugging Enhancements
3. Reporting improvements
4. New HTTP Request UI & HTTP Request Defaults
5. JSON Post Processor

2. New UI/UX:
JMeter 3 have complete new UI. You will see new icons on the UI. On the right side of the
toolbar you will find some new icons/elements, like one element shows the elapsed time
of a running test and one show icon tells whether test is ON or OFF.

3. Scripting and Debugging Enhancements:
1. New validation feature:​ ​This feature allow you to run selected Thread
Groups with only 1 user, no pause, and 1 iteration. Eg If you have a Thread
Group that have Threads: 10, Ramp-up time:2 second, Loop count: 5. By
using this feature you will be able to run that Thread Group with 1 user,
NO Ramp-up time will included and NO loop. To use this validation feature
right click on Thread Group then you will see validate option, just click on
it.

4. 2. New Search Feature in the View Results Tree:​ ​ ​This allows you to
search for text / regexp in Request/Responses/Headers/Cookies/. Early we
were able to find text / regexp in one request at a time, now we can find
text / regexp in View Results Tree.
3. Shortcuts to insert elements:​ This feature allow you to quickly add
elements into the test plan.
○ Ctrl + 0: Add New Thread Group
○ Ctrl + 1: Add New HTTP Request
○ Ctrl + 2: Add New Regular Expression Extractor
○ Ctrl + 3: Add New Response Assertion
○ Ctrl + 4: Add New Constant Timer
○ Ctrl + 5: Add New Test Action
○ Ctrl + 6: Add New JSR223 PostProcessor
○ Ctrl + 7: Add New JSR223 PreProcessor
○ Ctrl + 8: Add New Debug Sampler
○ Ctrl + 9: Add New View Results Tree

5. Reporting improvements:
JMeter3 have new various reporting enhancements such as:
● HTML Reporting Dashboard
● Generating dynamic Graphs in HTML pages (APDEX, Summary report, and
Graphs)
● Summariser displays a more readable duration
● BackendListener supports regular expression for sampler list
In Order to get JMeter Report Dashboard (UI that show all the reports). First copy
following line in ​user.properties​ file, you will find this file in jmeter bin folder.
jmeter.save.saveservice.bytes = true
jmeter.save.saveservice.label = true
jmeter.save.saveservice.latency = true
jmeter.save.saveservice.response_code = true
jmeter.save.saveservice.response_message = true
jmeter.save.saveservice.successful = true
jmeter.save.saveservice.thread_counts = true
jmeter.save.saveservice.thread_name = true
jmeter.save.saveservice.time = true
# the timestamp format must include the time and should include the date.
# For example the default, which is milliseconds since the epoch:
jmeter.save.saveservice.timestamp_format = ms
# Or the following would also be suitable
jmeter.save.saveservice.timestamp_format = yyyy/MM/dd HH:mm:ss

6. You can get Report Dashboard in the end of load test and by using ​existing csv log file​.
1. Getting Report Dashboard in the end of load test:
Goto terminal and run your jmeter(jmx) file in following manner:
jmeter -n ​-t jmeter3_demo.jmx​ ​-l report.csv​ -e ​-o
/home/lucifer/jmeter_rnd/jmeter3/new_reports
Above command:
● Jmeter​ : is to run jmeter itself
● -n​ : To run jmeter in NON UI mode
● -t​ : To specify your jmeter file (in my case it is ​jmeter3_demo.jmx​)
● -l​ : The file to log samples to (in my case i am logging in ​report.csv​)
● -e ​: Generate report dashboard after load test
● -o​ : Output folder for report dashboard(in my case it is
/home/lucifer/projects/jmeter_rnd/jmeter3/new_reports, ​ where you will
find your ​index.html ​after test and this html will launch Report
Dashboard)
2. By using existing csv log file:
To generate report dashboard by existing log file. Goto terminal and run following
command :
jmeter ​-g report.csv​ ​-o /home/lucifer/jmeter_rnd/jmeter3/new_reports
This Report Dashboard provides
● Dynamic HTML reports can now be generated at the start or end of a load test or a result
file
● You can now generate dynamic graphs in HTML pages
● Added a request summary graph showing successful and failed transaction percentages
● Support for APDEX
● Zoomable charts & graphs

7. On the dashboard you will see APDEX(Application Performance Index) table, request
summary graph, a statistics table, an error table.
You can find all the graph in Charts tab:
1. Over Time:
a. Response Times Over Time
b. Bytes Throughput Over Time
c. Latencies Over Time
2. Throughput:
a. Hits Per Second
b. Codes Per Second
c. Transactions Per Second
d. Response Time Vs Request
e. Latency Vs Request
3. Response Time:
a. Response Time Percentiles
b. Active Threads Over Time
c. Time Vs Threads
d. Response Time Distribution

8. ● Report Dashboard:
● A Statistics table providing in one table a summary of all metrics per transaction.
● An error table providing a summary of all errors and their proportion in the total requests.

9. ● Response Times Over Time: ​This graph represents the average response time over
time.
Y-axis represents : Average Response Time(ms)
X-axis represents: Elapsed Time
● Bytes throughput Over Time : ​This graph represents the throughput of received and
sent data over time.
Y-axis represents : Bytes per sec
X-axis represents: Elapsed Time

10. ● Latencies Over Time: ​This graph represents the average latency time over timeas
Y-axis represents : Average Response Latency(ms)
X-axis represents: Elapsed Time.
● Hits per second : ​This graph represents the rate of finished requests over time.
Y-axis represents : Number of Hits per sec
X-axis represents: Elapsed Time.

11. ● Response codes per second: ​This graph represents the rate of response codes over
time.
Y-axis represents : Number of Responses per sec
X-axis represents: Elapsed Time.
● Transactions per second: ​This graph represents the rate of transaction by sample
name over time.
Y-axis represents : Number of Responses per sec
X-axis represents: Elapsed Time.

12. ● Response Time vs Request per second : ​This graph represents the median and
average response time depending on the number of current requests.
Y-axis represents : Median Responses time(ms)
X-axis represents: Global number of requests per second.
● Latency vs Request per second: ​This graph represents the median and average
latency time depending on the number of current requests.
Y-axis represents : Median latency
X-axis represents: Global number of requests per second.

13. ● Response times percentiles : ​This graph represents the percentiles of the elapsed
time over time.
Y-axis represents : Percentile Value(ms)
X-axis represents: Percentiles.
● Active Threads Over Time : ​This graph represents all the active threads running in test.
Y-axis represents : Number of Active Threads
X-axis represents: Elapsed time.

14. ● Times vs Threads : ​This graph represents the average response time depending on the
number of current active threads.
Y-axis represents: Average Response Time(ms)
X-axis represents: Number of Active Threads.
● Response Time Distribution : ​This graph represents the distribution of the samples
depending on their elapsed time and name.
Y-axis represents: NUmber of Responses
X-axis represents: Response Time(ms

15. New HTTP Request UI & HTTP Request Defaults:
JMeter3 provided a new "Advanced" tab in HTTP Request and HTTP Request Defaults.
This tab is added to HTTP Request to simplify configuration. The file upload feature has
been moved into a dedicated tab, next to body data.
In HTTP Request Defaults, using the Advanced tab you can now configure Source
Address (IP Spoofing like feature) and "Save response as MD5 hash" in Advanced Tab.
HTTP Request
HTTP Request Defaults

16. JSON Post Processor:
This post processor is very similar to Regular Expression Post Processor but is well suited
for JSON code. Earlier we were not able to read JSON response (require some extra
configuration to be able to correctly send the JSON data), in order to check response
matches expectations or to extract data from response is important. This JSON post
processor lets you modify requests, matches expectations and data extraction.
Thank You
Pankaj Biswas