by general » Thu Apr 03, 2008 9:48 am
Here's the sequence of pages, below...hope it is helpful.
From what I know your best bet right now is to concentrate
on recording a sequence of steps, validating data into the
script along the way, so you can make a point test of one
function of the way your system works.
Then, experiment with variations of that script to see what
eValid does in various situations.
I think that a well-designed suite of functional tests that
exercise principal functions of the application will be a big
quality confidence builder.
eValid Tech Support Team