Thanks for taking time to post...
Good practice: one test for each application. Lots of
separate tests so that one test's failure does not mask
another test's success or failure.
* eValid uses a very generic script language that is simple and easy to
understand. The complete eValid script language is defined at:
http://www.e-Valid.com/Products/Documen ... cript.htmlLook up the "email" command.
* eValid, during playback, has ERROR, WARNING, ALARM and TIMEOUT flags that can be used to adjust the flow of control as described here:
http://www.e-Valid.com/Products/Documen ... rting.html http://www.e-Valid.com/Products/Documen ... .html#flag