Thanks for writing.
An eValid functional test script is ALSO the script that
a full-fidelity LoadTest run executes.
eVlite executes that same script, but only pays attention
to a subset of the commands (eVlite does not browser, it
just uses HTTP).
Or, you can automatically generate from script.evs a script
called URL.script.evs, which captures every URL retrieval
in script.evs.
* eValid provides a built-in feature that converts a full-context
playback script into the sequence of URLs that playback involves
(but which does not include any context preservation), as described
here:
http://www.e-Valid.com/Products/Documen ... trace.htmlThe main point is, why have a separate recorder or even
a converter to a "virtual user" when you don't have to?
Also, if you run 200 eValid's you can every one of them
run a completely different script if you want...