Here are the main points.
(1) Your Aim #1 is to do load testing, and eValid does that
by firrst doing a functional test, and then running multiple
browsers in parallel to impose load.
(2) The script is the same as a functional test, so your load
test is 100% realistic...it really IS multiple users all running
independently...
(3) Monitoring is simply functional testing on a regular basis,
and for eValid you use the Windows scheduler to run a batch
program that calls eValid.
eValid has ~60 switches that control executions from the Windows command
line, described here:
http://www.e-Valid.com/Products/Documen ... rface.html(4) The point here is that eValid's playback engine accomplishes
all of your goals...from the same script. The differences are
that for loading you run N of them in parallel, for montoring you
run the engine according to a schedule, and for functional testing
you can run in the foreground...
Please use the eValid license and try it yourself. It is VERY
easy to create and run tests!