Internal Timings

[Tester08]

Can eValid be used for drive load tests

Items to consider:

1) Throughput time for a single transaction - If it takes 15 seconds to
send a document manually, the script tool should be close to this time
as well.

2) A single browser will then drive 30 transactions in a row. eValid
will need to count these transactions which should matches the 30
documents sent to the local folder

3) We then need to drive our manager application with loads from 2 or
more browsers running the same script - There should then be 60
documents in the local folder. This may be difficult and may require
some king of IP spoofing mechanism to work.

[serverloading]

Thanks for posting.

(1) eValid is a browser and it is actually a bit more efficient
than IE is...so the timings ought to be 100% realistic and
accurate.

(2) Serial play with a repeat of one script 30 times, or
serial play with one script varied 30 times...either one is
OK out of the box...from the foreground.

(3) If you have one script from (2) working, then putting
two in parallel is easy...with the LoadTest engine (backup,
do it from batch/command line invocations)...