] > I've seen programs that can monitor your keystrokes and mouse clicks, etc,
] Danger alert! Danger alert! ] to look at the batch job, will jiggle the mouse, then everything breaks. ] Both approaches will be far more reliable than trying to drive a ] gui programmatically. ] It can. Been there, done that, have the scars. The professional testing & load-generation tools gave up on literal mouse (x= / y=) and key click capture/reply (more than?) several years ago for all the reasons Ben itemizes. The pros now use the Windows debugger interface and/or windows GUI introspection interfaces to ask the windows GUI sub-components their names, remember *WHAT* was clicked upon, and what had focus when things were typed, and to replay semantic actions -- push / click / type / submit TO THIS WIDGET. If you can't make it replay with OLE or commandline ... consider purchasing a real testing tool built for this purpose. You can script that, and be much happier. ( This assumes you're testing a non-Perl native Windows GUI, not the web-service it connects to. If instead you are testing a website/webservice and this is all about just driving it through IE, well, just use WWW::Mechanize instead of IE.) Bill NOT SPEAKING FOR THE FIRM _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
