Running a recorded script on command line with Jmeter gives Null Pointer Exception

Question

I record the test script using Blaze Meter and run it on GUI of Jmeter, it works fine.

But the same script when running on Command Line gives Null Pointer. Why would this be the case?

My second question is: Can I manipulate the Same Recorded script with CSV DataSet Config in order to Login with Multiple Users?

Here is Script In GUI in which I want to modify it with CSV DataSetConfig

Answer 1

• To sort out this null pointer I would recommend taking the next steps:

  1. Temporarily enable logging of requests and responses details by adding the next lines to user.properties file (located under "bin" folder of your JMeter installation)

     jmeter.save.saveservice.response_data=true
     jmeter.save.saveservice.samplerData=true
     jmeter.save.saveservice.requestHeaders=true
     jmeter.save.saveservice.url=true
     jmeter.save.saveservice.responseHeaders=true
     

     See Apache JMeter Properties Customization Guide to learn more about JMeter properties and ways of setting/overriding them.

  2. Run your test in command-line non-GUI mode

  3. Once test finishes open .jtl results file with View Results Tree listener and see requests and response details in it. Compare them with the ones you are getting in GUI mode. Additionally you may need to check jmeter.log file for any errors.

• To parameterize your test, if you need to use a new userName and you have a file with usernames list you can amend your request body like:

  {"userName" : "${__StringFromFile(/path/to/file/with/usernames.csv,,,)}"}
  

  Above __StringFromFile() function returns new line from the given file each time being called so each JMeter thread (virtual user) will send a new username

Answer 2

I have figured out why I was not able to run the recorded script.

By default, the ramp up period is zero. When I set some value in the file, save it, and run it in Non GUI mode, it works.

I still haven't figured out the CSV issue.