First, you do not need to load test a background job, which means you do not need loadrunner for batch testing. batch jobs are always tested by running the actual batch job, the same way, under the same controls of a production environment, and then you check how long did it take, you ask the questions of, did it run within a reasonable amount of time relative to the amount of data and transactions processed? then you check the CPU utilization used by that work process, if the jobs eats a lot of CPU then a re-design of the batch job needs to be considered, or if possible, in certain situation, i see that they split the job into two or three jobs to accomplish the same, and they be run one after another, to minimize the impact on the system resources and still achieve whats is needed from this background job
you can include batch testing in your performance testing cycle, however, you cannot use loadrunner really, batch jobs are run once, not multiple users are going to run the same job, matter of fact, thats out questions!!!!
Thanks
M. Azar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.