I want to print to dashboard report the loading details.
In case of Thread Group:
threads: 100
ramp up: 10
loop: 1
In case of Ultimate Thread Group: the Threads Schedule details
Is there a way to add them to the report?
Dotan
You can rename the JMeter's dashboard to reflect your load pattern, the relevant property is jmeter.reportgenerator.report_title so if you do something like:
jmeter -Jjmeter.reportgenerator.report_title="threads: 100 ramp up: 10 loop: 1" -n -t test.jmx -f -l result.jtl -e -o dashboard
the dashboard title will be changed to the property value:
More information:
Configuring JMeter
Apache JMeter Properties Customization Guide
Related
I am new to JMeter so bear with me...
I have a setUp Thread Group where I am grabbing a token and then re-using that in the HTTP Header Manager within the main Thread Group. Within that Thread Group I have the following parameters set...
I run this command to execute the tests:
jmeter -n -t PSC_Token.jmx -l testPsc.jtl -f
When I open the testPsc.jtl file though in Summary Report, I would expect that each request would show 600 for # Samples (200 threads * 3 loop count) but it is showing 1200 for each.
I tried deleting the file entirely and re-running it, just in case it was appending or something strange. That doesn't resolve the issue though.
Any ideas?
You're writing the same data into the same file 2 times, the options are in:
Disable (or better delete) the Summary Report listener, in general Listeners don't add any value, they only consume resources
Or remove -l command line argument and run your test just like:
jmeter -n -t PSC_Token.jmx
Also be aware that according to JMeter Best Practices you should always be using the latest version of JMeter so consider upgrading to JMeter 5.5 (or whatever is the latest stable version available at JMeter Downloads page)
let say i want to test the same http request for 10 users, 25 users ,50 users and 100 users separately and generate a report for each group of users.
One solution is to manually create as many thread group as a number of group of users:
ThreadGroup for 10 users
ThreadGroup for 25 users
...
is there any other solution to create this plan in jmeter?
Define the desired number of threads using __P() function like:
${__P(threads,)}
When you will be running JMeter in command-line non-GUI mode you will be able to pass the number of threads using -J command-line argument like:
jmeter -Jthreads=10 -n -t test.jmx -l 10-threads-result.jtl
jmeter -Jthreads=25 -n -t test.jmx -l 25-threads-result.jtl
etc.
I have used {__time(DD-MM-YYYY)} to save Jmeter results, results are saving successfully but date is returning like 32-03-2019, 33-03-2019, etc
According to docs you should use pattern for SimpleDateFormat:
D - Day in year
d - Day in month
Note also that
y - Year
Y - Week year
so you propably want to use dd-MM-yyyy
Most probably you're going into wrong direction. If you're using this function in the Listener - you should reconsider your approach as Listeners don't add any value, listeners just consume a lot of resources and being evaluated after each sampler
You should be running your tests in command-line non-GUI mode like:
jmeter -n -t test.jmx -l result.jtl
if you need to customise the result.jtl file to add a timestamp to it - go for command-line interpreter of your operating system features.
For example on Windows it would be something like:
jmeter -n -t test.jmx -l %date:~7,2%-%date:~4,2%-%date:~10,4%-result.jtl
on Linux/Unix/MacOS (given Bash shell)
./jmeter -n -t test.jmx -l `date +%d-%m-%Y-result.jtl
I have a script, one of the requests in the script is: redireccion.html, but when I generate the HTML Dashboard report I see:
redireccion.html-0, redireccion.html-1, redireccion.html-2
Why those requests are generated by Jmeter?
HTML Dashboard Report Graph
This happens when your first request i.e. redireccion.html encounters a HTTP Redirect, i.e. gets a Redirection Message
JMeter stores all these redirects as sub-results
If you don't want these sub-results to be present in the HTML Reporting Dashboard - you can run your test providing jmeter.save.saveservice.subresults property with the value of false like:
jmeter -Jjmeter.save.saveservice.subresults=false -n -t test.jmx -l result.jtl -e -o dashboard
In order to make the change permanent - just add the next line to user.properties file:
jmeter.save.saveservice.subresults=false
More information: Apache JMeter Properties Customization Guide
I have the following scenario:
Thread group1 - this sends requests to a server (lots of threads and iterations)
HTTP Request
Thread group2 - 1 thread 1 iterations
JSR223 sampler (has a while loop which periodically check if a number is 0) and collects some times
The scenario ends when threadgroup 2 finishes
I run the above scenario using the non GUI mode and i am interested in the RPS. (as shown below 222.0/s), but only for the first threadGroup.
summary = 50002 in 00:03:29 = 222.0/s Avg: 4151 Min: 38 Max: 797601 Err: 0 (0.00%)
Now, when the last threadGroup ends i will have:
summary = 50003 in 00:09:12 = 90.7/s Avg: 4136 Min: 38 Max: 797601 Err: 0 (0.00%)
The RPS is now low only because the last threadGroup takes very long to finish.
Is there any way the time from the last threadGroup can not be taken into consideration of the total time ? Or maybe another approach to this problem.
You can use jmeter.reportgenerator.sample_filter property in order to exclude your JSR223 Sampler from the report.
Run your test in command-line non-GUI mode like:
jmeter -n -t test.jmx -l result.jtl
The command to generate FULL results would look like:
jmeter -g result.jtl -o ALL-RESULTS
It will create ALL-RESULTS folder holding information on all the samplers
The command to generate results WITHOUT JSR223 Sampler would be:
jmeter -Jjmeter.reportgenerator.sample_filter="^((?!JSR223 Sampler).)*$" -g result.jtl -o FILTERED-RESULTS
It will create FILTERED-RESULTS folder with HTTP Request sampler only (or whatever else samplers, only JSR223 Sampler(s) will be excluded.
More information:
Generating Report Dashboard
Configuring JMeter
Apache JMeter Properties Customization Guide