Couldn't the printer be configured to not accept print jobs from whichever user(s)? In your case you would want to configure it to reject print jobs from whatever ID's your Virtual Users will be using.
I've never done this I'm just assuming it can be done.
SteveO: haha.. yeah could print to 'dead' printer. Was hoping for something a bit more realistic related to time/confirmation of print job being accepted/executed.
Interesting idea LR421; will research that possibility. ...and I completely agree PTRussell: don't want to trash trees and toner if at all possible. I'm just a bit naive to this request/need and was wondering if there was an 'emulator' or use of a 'soft-copy' printer setting which could be set as default to create the 1k's of requests.
Most the Pro printers have inbuilt RAM to store the jobs. These printers can be configured not to print automatically and any new print request gets added to each user's queue. All these requests should also be cleared down in one shot from the printer or by sending a purge/cancel request from the client (not sure about the latter as never tried it)
If you don't have such printer then jam a paper in your printer and it won't print [img]/images/graemlins/smile.gif[/img]
First off, is it the actual printing that you want tested? I would like to think that in any situation where there is a need for large number of paper prints there is a print server involved. If that is the case the print server (be it built into the printer(s) or on separate hardware) is what you want to focus on. Most print servers are very configurable, so setting up purging or implementing any other of the suggestions found here shouldn't be a huge problem.
In one project I found out I could set a flag in the print request (to an application server) which made the print server put my prints on a different queue, which I had a script purge at intervals.