Controller in loadrunner

Question

I’m planning to create an order entry transaction, using 30 vusers I’ll be running it and will be saving the order numbers in a param list (I hope this is possible).

Now, I need to create a transaction to verify orders, using the param list I’ve created above, My question is if I use 30 vusers how would they pick the order numbers? Once 30 vusers are started is there a possible conflict of two users picking the same order number?

Please explain how this works and the best possible solution to achieve the above task.

Answer 1

You could try LoadRunner VTS component. It allow you saving you parameters. And if you want to avoid conflict for these parameter, you can retrieve a parameter from VTS. This means read and delete the first line of the table. And you could append it at the end of the table if you want. More detail could be found from VuGen Help->Additional Compoenents->Virtual Table Server

Answer 2

In Loadrunner you cannot dynamically update the parameter list during test execution.(Reason: Parameter files will be saved in Load agent machines during test execution)

You can save the "Order Entry" to a simple text file. In Verify Order you can create a parameter "paramname" with parameter type "Vuser ID" and read the file data with respect to Vuser ID.

Eg: if "paramname" value is 2 then read the line number 2 from text file that you have created earlier.

Answer 3

If you write a parameter to a file you are going to have all sorts of issues

1. Managing lock for multiple users on the same file, likely across load generators. This alone can turn this one file into a bottleneck for your test as everyone waits for arbitrated access to the lock on the file
2. Parameter files are loaded into RAM at the beginning of the test, so you will not be able to use the parameters within the context of the same test.

Workaround: You could validate with a simple web_reg...() function within the same business process. This would be the lightest weight method.

If you need to share between virtual users where user A creates and user B validates then you need a queue or service to pass the information between. In such a case HP offers the Virtual Table Server as a service for just this type of operation. You can, however, leverage any external queue service, even using a managed service such as Amazon Simple Queuing Service, for this type of storage in between users where one user "pushes" the data and another "pops" it for validation.