A brief look at the execution order of each element jmeter:
First to carry out a classification of the various components:
Sampler (HTTP request, FTP request, TCP sampler, JDBC Request)
Logic controller (controller cycle, then the controller, the controller the while, if (IF) controller)
Timer (fixed timer, Uniform Random Timer, uniform random timer)
Assert (assertion response, XML assertions, JSON assertion, XPATH assertion, the size of the assertion)
Listener (graphical results, reported the polymerization, the resulting tree view, jp @ gc-hits per second, jp @ gc-connect times over time)
Configuration elements (CSV data file is provided, HTTP request header, HTTP Cookies manager, HTTP requests the default)
Take a look at elements of order execution, order execution rules are simple elements, in the same role in the domain range, test plan elements perform the following sequence.
(1) Configuration element (config elements)
(2) pre-processing procedure (Per-processors)
(3) timers (timers)
(4) sampler (Sampler)
(5) post processing (Post-processors) (unless Sampler returns the result obtained is empty).
(6) assert (Assertions) (return unless Sampler get results is empty).
(7) the listener (the Listeners) (returns the results obtained unless Sampler empty).
On the implementation of the order, there are two points to note:
* Preprocessor, and postprocessor assertions male element can, therefore, without any sampling in their role within the scope of the sampler, it will not be executed.
* If there are a plurality of elements of the same type in the same scope range, once these elements are performed in the vertical order in the test plan.