Glad to hear things are working OK.
(1) Yes, in the main mode of use eValid records validation facts
at the time of the recording, and saves details like the page
element index value (idx) in the script so the Adaptive Playback
feature can "do the right thing" for you at test playback time.
But, you can alter the script easily enough -- it is a simple text file --
to change what you are validating against.
You can even hand-edit a different idx value if you know what it is,
or you can put in a "0" for the idx if you want eValid to apply
the Adaptive Playback feature to kick in.
(2) The alternative route is to take advantage of the fact that
the script can be edited to include a range of DOM manipulation
commands.
You've not said specifically how that "column total" is organized,
but if you know the value in advance, you can modify the script
to be the expected value.
(3) The next level would be to provide the expected value by
some external means and save it in a local file. Then you
could have eValid write out the actual value from the page and
compare the two values, maybe with a SystemCallWait command.
eValid has special commands to allow input and output of DOM values
described here:
http://www.e-Valid.com/Products/Documen ... utput.htmlYou also could do this the other way, using eValid's DOM value manipulation
commands, described here:
http://www.e-Valid.com/Products/Documen ... ation.html_______________________
eValid Support Team