...
In this section, you will learn how to create a basic Test Plan to test a database server. You will create ten users that send five SQL requests to the database server. Also, you will tell the users to run their tests three times. So, the total number of requests is (10 users) x (2 requests) x (repeat 3 times) = 60 JDBC requests. To construct the Test Plan, you will use the following elements: Thread Group , JDBC Request , Graph Results .
No Format |
---|
This example uses the PostgreSQL org.postgresql.Driver database driver. To use this driver, its containing .jar file must be copied to the extension .../lib/ directory (see JMeter's Classpath for more details). Otherwise, expect a substantial amount of stack traces when running this test plan. |
Adding Users
The first step you want to do with every JMeter Test Plan is to add a Thread Group element. The Thread Group tells JMeter the number of users you want to simulate, how often the users should send requests, and the how many requests they should send.
...
Start by providing a more descriptive name for our Thread Group. In the name field, enter JDBC Users.
No Format |
---|
You will need a valid database, database table, and user-level access to that table. In the example shown here, the database is 'mydb' and the tables' name is 'Stocks'. |
Next, increase the number of users (called threads) to 10.
...
Finally, clear the checkbox labeled "Forever", and enter a value of 3 in the Loop Count field. This property tells JMeter how many times to repeat your test. If you enter a loop count value of 0, then JMeter will run your test only once. To have JMeter repeatedly run your Test Plan, select the Forever checkbox.
No Format |
---|
In most applications, you have to manually accept changes you make in a Control Panel. However, in JMeter, the Control Panel automatically accepts your changes as you make them. If you change the name of an element, the tree will be updated with the new text after you leave the Control Panel (for example, when selecting another tree element). |
See Figure 7.2 for the completed JDBC Users Thread Group.
...
Now that we have defined our users, it is time to define the tasks that they will be performing. In this section, you will specify the JDBC requests to perform.
No Format |
---|
Although there are JDBC Database Connection Pool Defaults , JDBC Database Login Defaults , and JDBC SQL Query Defaults components, they will not be used in this example. |
Begin by selecting the JDBC Users element. Click your right mouse button to get the Add menu, and then select Add --> Sampler --> JDBC Request. Then, select this new element to view its Control Panel (see Figure 7.3).
...