I have created many jmeter scripts using the GUI then created bash scripts to run them headless. Occasionally using sed to modify them on the fly when I couldn't get what I wanted just through parameters.
Writing a jmx file from scratch strikes me as the really hard way to go. John Sent from my iPhone > On Feb 20, 2016, at 5:14 PM, Mark Miller <[email protected]> wrote: > > It seems more practical, to me, to develop your test plan in an environment > where you have the support of the UI. Then move your test plan (.jmx) to > the ubuntu machine and invoke that test with -n (headless) and the other > logging params etc. so that you can review your results from that context. > > I'm sure it's possible to initiate a jmx file without the benefit of the > UI, but you'd only approach doing so from a place of general mastery with > JMeter (my opinion). > > Hope that helps. > > Mark > > On Sat, Feb 20, 2016 at 11:25 AM Richard Friedman <[email protected]> > wrote: > >> Why not use the OS Sampler? >> >> http://jmeter.apache.org/usermanual/component_reference.html#OS_Process_Sampler >> >> Here is a quick one I just created. >> >> >> >> On Sat, Feb 20, 2016 at 12:57 PM, Sheetal Jharia Baru <[email protected] >>> wrote: >> >>> Hi, >>> I have installed Jmeter on my ubuntu machine which doesnt have UI enabled. >>> I know I can run jmeter on CLI but I would need to create the .jmx file >>> for >>> running the shell script/command which I want to test. >>> Any sample .jmx fle which can run a command on shell will be helpful. I >>> can >>> make appropriate changes to it as per my environment. >>> >>> Thanks for the help ! >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
