Your e-Business Quality Partner eValid™ -- The Web Quality Suite
Browser-Based Client-Side Functional Testing and Validation Page Timing/Tuning Transaction Monitoring. WebSite Spidering & Analysis and Realistic Server Loading.
© Copyright 2000-2011 by Software Research, Inc.

eValid -- Power User Tips & Tricks
Prior   |   Catalog   |   eValid Home   |   Search   |   Next

Become an eValid Power User!
eValid Power User's Tips and Tricks can help you use eValid to get better results, quicker, and easier. Each Tips and Tricks item addresss one or two issues that will help you to increase your effectiveness with eValid.

> Using eValid for Training Demos

  The record/play nature of eValid can make for very effective
  illustrative demos and training sequences.  These scripts play
  back automatically, and can include informative messages and popup
  windows.  This can be a real winner at a tradeshow or an in-house
  demo!

  * Making the Script:  Start with the basic record/play script done
    as if you were testing the application.

    Add Wait's to time the script carefully.  Be careful not to use
    a Delay Multiplier value that cancels your Waits!

    Edit in MessageBox or MessageWindow commands to annotate the
    script as it plays back.

    You can even edit in audio playbacks (using eValid's SystemCall
    command).

  * Structuring Your Demos:  It should be easy to develop eValid
    playback scripts that follow this kind of overall structure for
    your demos:

    (1) Setup: A script to start up the application on the desktop
        and make sure everything each demo needs is in the correct
        place and configuration and state.

    (2) Demo Scripts: These all start from the result of (1) and
        illustrate various kinds of features of the application.
        Each one asks at the end "Do you want to try additional
        eValid demo scripts?"  and if then answer is No, then eValid
        automatically go to (3), using an OnErrorGoScript command.
        Otherwise, you would select another file to play back (demo
        to run).

    (3) Cleanup: Script to "close down" the application so that the
        next instance of (1) is be trouble-free.

  * Caution:  Our experience with demo scripts is that it takes, on
    average, several hours per demo script to make them work well
    and also be good tutorial material.  Careful planning is the key
    to a successful demo script!