Category:
JMeter
Configuration elements can be used to set up defaults and variables for later use by samplers.
Types of Config Elements:
CSV Data Set Config – CSV Data Set Config is used to read lines from a file, and split them into variables. We can use __CSVRead() and _StringFromFile() JMeter in built functions to read data from file.
By default, the file is only opened once, and each thread will use a different line from the file. However the order in which lines are passed to threads depends on the order in which they execute, which may vary between iterations. Lines are read at the start of each test iteration.
| FTP Request Defaults | FTP Request Defaults config element is associated with FTP Request Sampler. This element is used when your going to send multiple requests to same FTP server. |
| HTTP Authorization Manager | The Authorization Manager lets you specify one or more user logins for web pages that are restricted using server authentication. You see this type of authentication when you use your browser to access a restricted page, and your browser displays a login dialog box. JMeter transmits the login information when it encounters this type of page. |
| HTTP Cookie Manager in Jmeter | Each JMeter thread has its own cookie storage area. The use of cookies eventually becomes necessary when your application has to maintain a session. Once you login to an application, it maintains the session of that user so that he/she can work inside the application. If that session is not maintained (via Cookie Manager in case of JMeter), then the user will be logged out of the application as soon as he/she sends the next request, which requires Authentication. You can take it like this, if your application has a session or uses cookies, then your script will not work without adding cookies in cookie manager, as then your script will not be able to maintain the session and the users (Threads) will be kicked-off the application as soon as they enter into it. Each JMeter thread has its cookie storage area. So, if you are testing a web site that uses a cookie for storing session information, each JMeter thread will have its session. |
| HTTP Request Defaults | This element lets you set default values that your HTTP Request controllers use. For example, if you are creating a Test Plan with 25 HTTP Request controllers and all of the requests are being sent to the same server, you could add a single HTTP Request Defaults element with the “Server Name or IP” field filled in. Then, when you add the 25 HTTP Request controllers, leave the “Server Name or IP” field empty. The controllers will inherit this field value from the HTTP Request Defaults element. |
| HTTP Header Manager | The Header Manager lets you add or override HTTP request headers. Ex: User-Agent Accept Accept-Encoding Accept-Language |
| User Defined Variables | The User Defined Variables element lets you define an initial set of variables , just as in the Test Plan . Note that all the UDV elements in a test plan – no matter where they are – are processed at the start. UDVs can be used with functions such as __P(), for example: HOST ${__P(host,localhost)} |
| Counter | Allows the user to create a counter that can be referenced anywhere in the Thread Group. The counter config lets the user configure a starting point, a maximum, and the increment. The counter will loop from the start to the max, and then start over with the start, continuing on like that until the test is ended. |
| Login Config Element | The Login Config Element lets you add or override username and password settings in samplers. |
| Simple Config Element | ‘Simple Config Element’ is used to add or override arbitrary values in samplers. You can choose the name of the value and the value itself. |
| JAVA Request Defaults | ‘Java Request Defaults’ is used to set default parameters to pass them into Java Request. Sleep_time Sleep_mask Label Response Code ResponseMessage Status SamplerData ResultData |