java - JMeter execution -
i trying execute simple script in laptop.but below message , script doesn't execute. thread loop count set 3, tried adding header manager no luck. want see execution put in gui mode request doesn't hit. below log info , no error.
2015/05/31 00:41:23 info - jmeter.engine.standardjmeterengine: running test! 2015/05/31 00:41:23 info - jmeter.samplers.sampleevent: list of sample_variables: [] 2015/05/31 00:41:23 info - jmeter.gui.util.jmetermenubar: setrunning(true,*local*) 2015/05/31 00:41:23 info - jmeter.engine.standardjmeterengine: starting threadgroup: 1 : thread group 2015/05/31 00:41:23 info - jmeter.engine.standardjmeterengine: starting 1 threads group thread group. 2015/05/31 00:41:23 info - jmeter.engine.standardjmeterengine: thread continue on error 2015/05/31 00:41:23 info - jmeter.threads.threadgroup: starting thread group number 1 threads 1 ramp-up 0 perthread 0.0 delayedstart=false 2015/05/31 00:41:23 info - jmeter.threads.threadgroup: started thread group number 1 2015/05/31 00:41:23 info - jmeter.engine.standardjmeterengine: thread groups have been started 2015/05/31 00:41:23 info - jmeter.threads.jmeterthread: thread started: thread group 1-1 2015/05/31 00:41:23 info - jmeter.threads.jmeterthread: thread done: thread group 1-1 2015/05/31 00:41:23 info - jmeter.threads.jmeterthread: thread finished: thread group 1-1 2015/05/31 00:41:23 info - jmeter.engine.standardjmeterengine: notifying test listeners of end of test 2015/05/31 00:41:23 info - jmeter.gui.util.jmetermenubar: setrunning(false,*local*)
looking log file script finishes normally. best way visualise request , response details using view results tree listener, way able tell going on. listener handy debugging regular expressions, css , xpath queries, , checking variables , properties values in combination debug sampler
you can configure jmeter make logging more verbose. add log_level.jmeter=info
line user.properties file (it located in /bin folder of jmeter installation), restart jmeter , inspect jmeter.log file looking suspicious.
once figured out , fixed cause highly recommended revert changes back, wit:
- disable or delete view results tree listener (as other listeners)
- restore logging level "info" in case of massive load disk io usage logging system immense , may ruin test
Comments
Post a Comment