Introduction to JMeter Google PlugIn- Config elements
In this article we are going to see what are additional features/items added after installing jmeter plugin (Google Plugin) and what we can do with it. I will discuses about Config elements only. To know about basic of jmeter see my this page. And, the process to install plug in , see this post.
What does a Config element do? Basically it stores a configuration settings needed while executing tests. The google plug in provide you four types of config elements. I am describing all in above.
1. jp@gc - HBase Connection Config
This need spatial plugin library to be installed. Download link is here. Keep the files in \apache-jmeter-2.9\lib directory.
-Right click a Test Plan or thread > Config elements >jp@gc - HBase Connection Config
HBase Config element designed for defining connection to HBase which will be shared among the samples under test plan. We have to insert the connection name and the host server address(without http)
Note : I have not used this one in real life projects. So, I can add more when I have done using.
2. jp@gc - Lock File Config
-Right click a Test Plan or thread > Config elements > jp@gc - Lock File Config
-This allow jmeter to check for a specified file's lock status. This is necessary when ever the test plan have dependency over a file and jmeter can not run as the file is locked. Usually this happens when another application or another jmeter instance is occupying the file. It is helpful when we use CSV file for input or any file to store logs/results.
-It also allows us to specify a file which will be locked by jmeter at the beginning and deleted after test. Please careful that the mentioned file is not present in the path. It will show "Lock file found" error.
When the screenshot was taken , Jmeter was running so we could see the shantonu1.csv. When the test finished, it was deleted.
3. jp@gc - Variables From CSV File
-Right click a Test Plan or thread > Config elements >jp@gc - Variables From CSV File
The element contains following items.
CSV file : Default /bin directory pointed, so if you write only name , it will search bin directory of jmeter. It is the best to provide full path. (Ex- D:\Shantonu.csv)
Variable prefix: If we have used any prefix before our variable name, this plug will add the prefix text before of every variable it finds from CSV file.
Separator: We can mention our separator that we have used in the csv file. Default is comma(,). We can use tab(\t), and other symbols also.
Stored variable in system properties : This will allow to save variable to system.properties file present in /bin.
We can also test the pursed variable by clicking Test CSV file.
For the example : I have use these text in csv file
NAME,shantonu
OCC,Tester
"myV_" as prefix, And, comma(,) as separator. When we click test csv file, it will be shown like this.
And we have to use in the request as variable name ${myV_NAME} or ${myV_OCC}.
If there is any error after clicking test csv file, it will be shown in log message at the bottom.
We can see the data presence in response data tab of view result tree listener.
Thanks..:)
What does a Config element do? Basically it stores a configuration settings needed while executing tests. The google plug in provide you four types of config elements. I am describing all in above.
1. jp@gc - HBase Connection Config
This need spatial plugin library to be installed. Download link is here. Keep the files in \apache-jmeter-2.9\lib directory.
-Right click a Test Plan or thread > Config elements >jp@gc - HBase Connection Config
HBase Config element designed for defining connection to HBase which will be shared among the samples under test plan. We have to insert the connection name and the host server address(without http)
Note : I have not used this one in real life projects. So, I can add more when I have done using.
2. jp@gc - Lock File Config
-Right click a Test Plan or thread > Config elements > jp@gc - Lock File Config
-This allow jmeter to check for a specified file's lock status. This is necessary when ever the test plan have dependency over a file and jmeter can not run as the file is locked. Usually this happens when another application or another jmeter instance is occupying the file. It is helpful when we use CSV file for input or any file to store logs/results.
-It also allows us to specify a file which will be locked by jmeter at the beginning and deleted after test. Please careful that the mentioned file is not present in the path. It will show "Lock file found" error.
When the screenshot was taken , Jmeter was running so we could see the shantonu1.csv. When the test finished, it was deleted.
3. jp@gc - Variables From CSV File
-Right click a Test Plan or thread > Config elements >jp@gc - Variables From CSV File
The element contains following items.
CSV file : Default /bin directory pointed, so if you write only name , it will search bin directory of jmeter. It is the best to provide full path. (Ex- D:\Shantonu.csv)
Variable prefix: If we have used any prefix before our variable name, this plug will add the prefix text before of every variable it finds from CSV file.
Separator: We can mention our separator that we have used in the csv file. Default is comma(,). We can use tab(\t), and other symbols also.
Stored variable in system properties : This will allow to save variable to system.properties file present in /bin.
We can also test the pursed variable by clicking Test CSV file.
For the example : I have use these text in csv file
NAME,shantonu
OCC,Tester
"myV_" as prefix, And, comma(,) as separator. When we click test csv file, it will be shown like this.
And we have to use in the request as variable name ${myV_NAME} or ${myV_OCC}.
If there is any error after clicking test csv file, it will be shown in log message at the bottom.
We can see the data presence in response data tab of view result tree listener.
Thanks..:)