2. Building a Test Plan
A test plan describes a series of steps JMeter will execute when run. A complete test plan will consist of one or more Thread Groups, logic controllers, sample generating controllers, listeners, timers, assertions, and configuration elements.
2.1 Adding and Removing Elements¶
Adding elements to a test plan can be done by right-clicking on an element in the tree, and choosing a new element from the "add" list. Alternatively, elements can be loaded from file and added by choosing the "merge" or "open" option.
To remove an element, make sure the element is selected, right-click on the element, and choose the "remove" option.
2.2 Loading and Saving Elements¶
To load an element from file, right click on the existing tree elements to which you want to add the loaded element, and select the "merge" option. Choose the file where your elements are saved. JMeter will merge the elements into the tree.
To save tree elements, right click on an element and choose the "Save Selection As …" option. JMeter will save the element selected, plus all child elements beneath it. In this way, you can save test tree fragments and individual elements for later use.
2.3 Configuring Tree Elements¶
Any element in the test tree will present controls in JMeter's right-hand frame. These controls allow you to configure the behavior of that particular test element. What can be configured for an element depends on what type of element it is.
2.4 Saving the Test Plan¶
Although it is not required, we recommend that you save the Test Plan to a file before running it. To save the Test Plan, select "Save" or "Save Test Plan As …" from the File menu (with the latest release, it is no longer necessary to select the Test Plan element first).
2.5 Running a Test Plan¶
To run your test plan, choose "Start" (Control + r) from the "Run" menu item. When JMeter is running, it shows a small green box at the right hand end of the section just under the menu bar. You can also check the "Run" menu. If "Start" is disabled, and "Stop" is enabled, then JMeter is running your test plan (or, at least, it thinks it is).
The numbers to the left of the green box are the number of active threads / total number of threads. These only apply to a locally run test; they do not include any threads started on remote systems when using client-server mode.
2.6 Stopping a Test¶
There are two types of stop command available from the menu:
- Stop (Control + .) - stops the threads immediately if possible. Many samplers are Interruptible which means that active samples can be terminated early. The stop command will check that all threads have stopped within the default timeout, which is 5000 ms = 5 seconds. [This can be changed using the JMeter property jmeterengine.threadstop.wait] If the threads have not stopped, then a message is displayed. The Stop command can be retried, but if it fails, then it is necessary to exit JMeter to clean up.
- Shutdown (Control + ,) - requests the threads to stop at the end of any current work. Will not interrupt any active samples. The modal shutdown dialog box will remain active until all threads have stopped.
When running JMeter in CLI mode, there is no Menu, and JMeter does not react to keystrokes such as Control + ..
So JMeter CLI mode will listen for commands on a specific port (default 4445, see the JMeter property jmeterengine.nongui.port).
JMeter supports automatic choice of an alternate port if the default port is being used
(for example by another JMeter instance). In this case, JMeter will try the next higher port, continuing until
it reaches the JMeter property jmeterengine.nongui.maxport) which defaults to 4455.
If maxport is less than or equal to port, port scanning will not take place.
The chosen port is displayed in the console window.
The commands currently supported are:
- Shutdown - graceful shutdown
- StopTestNow - immediate shutdown
2.7 Error reporting¶
JMeter reports warnings and errors to the jmeter.log file, as well as some information on the test run itself. JMeter shows the number of warnings/errors found in jmeter.log file next to the warning icon (triangle) at the right hand end of its window. Click on the warning icon to show the jmeter.log file at the bottom of JMeter's window. Just occasionally there may be some errors that JMeter is unable to trap and log; these will appear on the command console. If a test is not behaving as you expect, please check the log file in case any errors have been reported (e.g. perhaps a syntax error in a function call).
Sampling errors (e.g. HTTP 404 - file not found) are not normally reported in the log file. Instead these are stored as attributes of the sample result. The status of a sample result can be seen in the various different Listeners.