There are several levels to this...
(1) The assertion capability -- eValid calls it "validation" -- can arise
from values that you extract during recording, or they can come from
commands that you edit in.
In the script, if you want to you can manually change the thing validated,
e.g. a text fragment, or you can also manually change the index eValid
recorded (that tells the playback where to look for it on the response
page, in the future).
(2) No, you don't have to toss the script at all. If you want to
add assertions you can use one of two routes:
(2A) Insert recording: You single step to the command that takes you
to the page where you want to add a validation, then "Insert Recording"
which will let you position the cursor at where you want the new validation.
Then, do the validation with the pulldown menus, and stop recording.
The new script will have the added validation in the right spot.
(2B) Manual insertion: You can edit in any of the 20+ validation
commands into the script at any point you wish.
Here is the complete description of eValid's Validation modes: http://www.e-Valid.com/Products/Documen ... ation.html
(3) To get really fancy, you can edit validations into the script on
things that you can't actually see. That is, they are on the page,
but not even visible (i.e. you can't highlight them).
eValid has a powerful built-in facility that lets you Validate
page properties in terms of the internal page DOM, and the capability
can also be used to set up Validations that apply Adaptive Playback
to prevent Validation failures when pages experience maintenance: http://www.e-Valid.com/Products/Documen ... bject.html
Hope this helps!
eValid Support Team