1. Yes, any script can be parameterized with $NAME type parameters,
which are then given values in a number of ways...
The eValid string substitution facility -- used in both functional
testing AND in server load creation -- is described here:
http://www.e-Valid.com/Products/Documen ... rings.htmlHere's a diagram of this process:
http://www.e-Valid.com/Products/Documen ... nsion.htmlThere is a built-in capability to pre-specify values for
parameters in an eValid script, described in detail here:
http://www.e-Valid.com/Products/Documen ... ables.htmlOr $NAME=value as command line arguments.
2. By check points I assume you mean validataions.
Here is the complete description of eValid's Validation modes:
http://www.e-Valid.com/Products/Documen ... ation.htmlThe Breakpoint command is decribed here:
http://www.e-Valid.com/Products/Documen ... Breakpoint3. The eValid command language does not have local variables...it
is NOT a programming language. See environment variables described
above. If there is something you need to do relative to a script
the combination of CallScript or environment variables usually
lets you do it...
My question back to you is, what are the criteria you're trying
to match eValid up against? If you have a functional test
that plays back in LoadTest mode what else do you need to do?