I can't record my chrome actions in Jmeter, because of below mentioned screen shot. Is there any suggestion for this ?
Your proxy.cert.directory setting is incorrect, you need to amend the property value to point to the "bin" folder of your JMeter installation.
If for any reason your user account doesn't have permissions to create files in JMeter's "bin" folder - set it to the location, you can create files at. The folder must exist.
proxy.cert.directory property can be set in at least 3 ways:
in jmeter.properties file (not recommended)
in user.properties file (recommended for permanent changes)
via -J command-line argument (recommended for temporary changes)
JMeter restart will be required to pick the property up.
See HTTPS recording and certificates chapter of the HTTP(S) Test Script Recorder User Manual entry and Apache JMeter Properties Customization Guide for more details.
Related
I am outputting results from 30 tests to a single xml file.
Currently the file includes latency, connection time, and whether it returned OK. I want the endpoint I am hitting to also be shown. My tests run in sequence and output to a single file.
It's Save URL checkbox:
You can also achieve the same by amending JMeter Results File Configuration like:
jmeter.save.saveservice.output_format=xml
jmeter.save.saveservice.time=true
jmeter.save.saveservice.filename=true
jmeter.save.saveservice.latency=true
jmeter.save.saveservice.response_code=true
jmeter.save.saveservice.url=true
and others set to false
Put your changes to user.properties file, JMeter restart will be required to activate the changes.
More information:
Configuring JMeter
Apache JMeter Properties Customization Guide
why am I getting this error while recording a test script in Jmeter ??
You're getting this error because JMeter cannot create file proxyserver.jks in its working folder.
Most probably the user doesn't have permissions to write anything to the folder where you're launching JMeter from. Just grant the user rights for writing into that folder and the error will go away. If you don't have enough rights for that - copy JMeter to the folder where you have write access to (normally it's your home directory)
Also be aware of an alternative way of recording a JMeter test: JMeter Chrome Extension, in this case you won't have to worry about proxies and SSL certificates. If you don't want or cannot use the Chrome extension due to organization restrictions at least consider using Recording Template as it creates a well-configured recording test plan in one click.
I'm using jmeter 3.2, I want run a SMTP Sampler in Jmeter where I have done the necessary configuration by adding the javamail file in the lib folder of Jmeter and adding necessary credentials in the mail setting, though when executed I am getting an error of IOException.
Am I missing any step?
There was a change in SMTP Sampler in jmeter 3.2 which created several bugs.
You open a bug to jmeter with a sample if it's a different scenario.
If you can downgrade to Jmeter 3.1 if it can work.
EDIT
You can download a fix to the issue in jmeter-3.3
If you are trying to send a file as an attachment you have 2 options:
If you are using relative path (just filename) make sure you put the file into JMeter's "bin" folder. So JMeter could find it. Check out jmeter.log file to know where JMeter is expecting the file to be.
Use full path (like c:\somefolder\someotherfolder\somefile.eml)
In case if you still experience the problem update your question with your email server configuration and jmeter.log file contents. In the meantime check out Load Testing Your Email Server: How to Send and Receive E-mails with JMeter article
I created a project like this:
I want to check the http response data, so used "Summary Report" and "Save Response to file" listeners, and I ran this project in remote mode, found that neither "Summary report" or "Save Response to file" output file was empty. If I ran this project in standalone mode, the output files saved repose data OK.
Am I using the listeners in a wrong way, or these kind of response listeners not support in the remote mode.
This is due to JMeter's default slave-master results sending mode StrippedBatch which removes response data from successful samples, see Using a different sample sender chapter of the Remote Testing User Manual chapter for detailed explanation of the available modes.
You can switch the mode via either adding the following line to user.properties file (located in JMeter's /bin folder)
mode=Standard
or pass it as a command-line argument to JMeter slave startup script as:
jmeter-server.bat -Jmode=Standard
See Apache JMeter Properties Customization Guide guide for more information on different JMeter properties types and ways of setting them and JMeter Distributed Testing Step-by-step guide for other remote testing tips.
My test plan use a parameter as startIndex.
In local case:
"thread pool 1" -> "Java Request" -> "Send Parameters With the Request" -> Add a parameter named startIndex,
and Create a config element - "User Defined variables", and give a parameter startIndex.
But how to give different startIndex parameters to each server,
for example:
serverA:"startIndex"=100, serverB:"startIndex"=200.
On each JMeter slave machine locate user.properties file under /bin folder of your JMeter installation
Add the following lines to this file:
on server 1: startIndex=100
on server 2: startIndex=200
Refer startIndex property value via __P() function as ${__P(startIndex,)} where required
Make sure you restart JMeter after user.properties file modification.
See Apache JMeter Properties Customization Guide for extended information on JMeter properties and ways of working with them
It is not a best practice to have create two variables having same names. If this situation is unavoidable then do not use 'user defined variables. Instead you can create the second variable under specific sampler, by using beanshell (vars.put) to create second variable. Not a tested technique but you can try.