Really need to chat you through, but here are some backup pages...
* Scripts that are to be played back in multi-threaded monitoring playbacks,
or for multi-usr load test scenarios, may need to be "desktop safe"
to prevent one [or more] playbacks from interfering with each other.
The "desktop safe" mode for eValid playbacks is described here:
http://www.e-Valid.com/Products/Documen ... .safe.html* eValid has ~60 switches that control executions from the Windows command
line, described here:
http://www.e-Valid.com/Products/Documen ... rface.html(You may need to specify DIFFERENT path names for two eValid's running
in parallel...)
* When you need to instruct an eValid script to grab control of the
desktop (e.g. when your script has to feed a mouse-click to an
Applet), you may need to use the Lock/Unlock command:
http://www.e-Valid.com/Products/Documen ... nlock.html
by monitoring » Fri Aug 15, 2008 4:21 pm