On 17/06/2010, roccatgaming <[email protected]> wrote: > > Hi, > > I am trying to run different jmx files by calling jmeter.sh from a custom sh > script that I've wrote. > The script file was supposed to run a test in Non-GUI mode and then move on > to the next one. > > The script file is like this: > > #----------------------------------------------------------- > ${JMETER_HOME}/bin/jmeter.sh -n -p ${TESTS_HOME}/test1.properties -t > ${TESTS_HOME}/test1.jmx > ${JMETER_HOME}/bin/jmeter.sh -n -p ${TESTS_HOME}/test2.properties -t > ${TESTS_HOME}/test2.jmx > ${JMETER_HOME}/bin/jmeter.sh -n -p ${TESTS_HOME}/test3.properties -t > ${TESTS_HOME}/test3.jmx > #-----------------------------------------------------------
That looks OK, though you might want to use separate jmeter log files (-j). Ditto for jtl files (-l). > > Note: If I run the tests without the -n parameter (so, in GUI mode) after I > close the first test the next one opens and so on. So it works as expected. > But, in Non-GUI mode, after running the first test, the JMeter prompts me > about "Tidying up ..." "... end of run" and nothing happens next. The next > test doesn't start. I think the script waits for something, or JMeter > doesn't shut down itself... I'm not sure. Check the log file to see. > Do I have to put a specific element in JMeter at test end? So that it close > itself? No, JMeter should shutdown by itself when all the threads have completed. Does the GUI mode test show all the threads as having completed, or are some still running when you close it? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
