Page History

...

• Wiki Markup

  In your existing test plan, make sure that any variations in testing make use of functions or variables. For example, if running a HTTP sampler, use HTTP Request Defaults to specify a host as {{$\{+P(targetHost,localhost)\}}}. Other useful places for parameterisation might include number of threads, ramp-up period or scheduler duration in a thread group, using a format of {{$\{+P(threadgroup.threads,500)\}}} (The {{+P}} function is shorthand for {{+property}}. See the \[http://jakartajmeter.apache.org/jmeter/usermanual/functions.html#__P user manual\] for more info on using this function).

• Save your test plan and properties file to a directory.
• Create a properties file containing all your variables. E.g. mytest.properties could contain threadgroup.threads=100, targetHost=my-target-host.com
• The test plan does not need Listeners, as this will be configured via parameters. This will improve performance on the testing.
• Run the test mode in stand-alone mode (i.e. no remote servers): jmeter -n -t load_test.jmx -l load_test_report.jtl -q mytest.properties -j mytest.log
• The "-q" parameter defines an additional property file, which is the equivalent of setting properties for the contents of the file using the -J parameter. These parameters are not sent to remote servers; for that one can use the -G parameter. The -G parameter can reference either a property in the format of -Gprop=val or a properties file, such as -G./myglobal.properties
• Properties can be referenced anywhere in the test plan using the +P() function - e.g. ${+P(propname)}
• There is no way currently to predefine variables, however the User Defined Variables table on the Test Plan can be used to create variables from properties. For example:

...