The question was already posted by Chintamani here however it has not been answered.
I'm trying to get the details of my error through the generated dashboard report by JMeter but it's not detailed out in the report. It just indicates that an assertion failed.
Rather than just indicating Assertion Failed in the Type of error. I would want for the report to display the custom response assertion error message that I indicated in the response assertion. I hope someone can help. Thanks!
EDITS:
I have replicated the issue here. It still indicating assertion failed. Not sure what I'm missing here. Also, I am using the updated JMeter version 5.2.1.
This is my result save configuration on my simple data writer.
I cannot reproduce your issue using latest stable JMeter version 5.2.1:
According to 9 Easy Solutions for a JMeter Load Test “Out of Memory” Failure you should be using the latest version of JMeter so consider upgrading to JMeter 5.2.1 (or whatever is the latest stable JMeter version which is available at JMeter Downloads page) and the issue will go away.
If you're using the latest version already it might be the case you're looking into "old" results, re-run your test providing -f command-line argument so JMeter would overwrite the previous .jtl results file and the dashboard folder with the new results
Check for properties jmeter.save.saveservice.assertion_results_failure_message=false
This should be equal to true or just remove/comment before running again.
Related
I am trying to execute a .jmx script in the GitHub. The login page requires a OTP, which I am generating using org.jboss.aerogear. However, it seems when I am executing the script in GitHub the script is not generating this OTP and throwing 406 (Not Acceptable). Can anyone please guide me on this issue please.
This is running perfectly in JMeter but getting error in GitHub.
Do I need to add this specific driver and how?
Whenever you face any "error" first of all take a look at jmeter.log file, normally it contains the reason or at least a clue so you can figure out or guess the error cause. If it doesn't - increase JMeter logging verbosity for the test elements you're using.
Most probably you need to add the .jar file which provides this Totp class (along with dependencies, if any) to JMeter Classpath to JMeter installation in "Github" (whatever it means) and the error will go away
while generating html report through jmeter getting following error message.
note[using jmeter version 5.4.1]
Generating report
An error occurred: Data exporter "html" is unable to export data.
The Data exporter "html" is unable to export data message unfortunately doesn't contain either root cause of the issue or at least a clue.
You need to take a look at jmeter.log file, it should contain way more information regarding the failure.
The most common reasons are:
Lack of JVM Heap space
Impossibility to write to the destination folder (lack of permissions, disk full, etc.)
Issues with .jtl results file (i.e. you ran your test on another JMeter instance having different Results File Configuration)
Also be informed 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 version available at JMeter Downloads page) on next available opportunity.
I'm facing a weird situation with Jmeter 5.4.1
When running a suite, in my results tree all I can see are the results from first 7 (of 30) tests, and in the report, 20 of 30 tests.
All calls are simple and have just a status code and body response assert, and nothing more.
Anyone aware about this issue?
I don't think it's "weird", it's "by design".
By default JMeter stores/shows 500 last results in the View Results Tree listener
If you want to remove this limitation you can add the next line to user.properties file:
view.results.tree.max_results=0
JMeter restart will be required to pick the property up. Then you will be able to see all the results (given they will fit into memory)
More information:
Configuring JMeter
Apache JMeter Properties Customization Guide
I am just wondering how I can control the number of requests in Taurus / Jmeter?
Let's say I have to use an external file where there are prepared data for the test. I have to know how many data I should make for data (i.e. how many requests will be fired by Taurus / JMeter).
I found this article which says that the throughput setting can be used for that. However I got the following exception when I added this single setting (throughput: 2) to my yaml file:
2018-05-31 13:08:11,743 ERROR o.a.j.JMeter: Error in NonGUIDriver
java.lang.IllegalArgumentException: Problem loading XML from:'/home/vikhor/projects/temp/taurus/test_SOAP/2018-05-31_13-07-54.930576/modified_requests.jmx', missing class com.thoughtworks.xstream.converters.ConversionException
...
Caused by: com.thoughtworks.xstream.mapper.CannotResolveClassException: kg.apc.jmeter.timers.VariableThroughputTimer
I haven't installed JMeter, let Taurus installed it.
Any idea how to fix this issue (found this link but didn't help) or how to control the number of the requests?
Please check if you have JPGC# Throughput Shaping Timer plugin installed with the jmeter.
Please check the below image:-
If you didnt find it then it may be the cause. Then, you can install it by any of the two methods:-
1- Use Jmeter plugin manager
2. Direct download the plugin
Prefer plugin manager as it will be helpful in future to install other plugins.
Hope it helps.
The same script works in jmeter 3.1 but not in jmeter 3.2, why?
Can someone answer that?
EDIT 1:
Open bug for jmeter.
There was a change in SMTP Sampler in jmeter 3.2
Which wasn't tested. I suggest you open a bug to jmeter with a sample.
If you can't post bug I can post it for you if you give sample jmx that doesn't work.
If you can downgrade to Jmeter 3.1 it can work.
I understand this is a fairly big change with no tests but I thought
I'd submit anyway in the hope that someone had some good SMTP tests or
someone was willing to review or even just apply a subset of the
changes.
There's also existing bug reported on SMTP Smapler in Jmeter 3.2.
EDIT
You can download a fix to the issue in jmeter-3.3
I got it to work in Jmeter 3.2.
I got the report stored in a file and gave the path to that file "Attach file(s)" section and its sending email successfully.