Testing the script
~~~~~~~~~~~~~~~~~~

        The previous 13 lessons have provided enough info to write a
complete mailrun script + a couple enhancements.  Once you have a
script, the next step is to test it.  The first test you should
perform is a "sanity check"..print the script and review each line
for obvious syntax errors (e.g., "missing" braces, extra spaces in
lines, "missing" macro IDs, misspelled commands, etc.).  Run through
the script in your mind, process by process..trace the sequence of
events from start to finish.

        After you're satisfied that there's nothing obviously wrong
with the script which would cause it to bomb out right away, it's
time to check it out on-line.  This part is real easy..you just sit
back and watch what happens.  Before you jump into this test, though,
be sure you have:

        -- already configured the mail door on the board, i.e.,
conferences you want scanned, protocol, etc., etc.

        -- already downloaded a mail packet from the BBS and have
generated a .REP.  You'll want to test everything the script is
supposed to do, which includes uploading a .REP if one exists.

        All right, it's time to run the script.  Bring up the dialing
directory.  Is the "Linked Macro" for the BBS you want to call the
correct macro?  Put the highlight bar over the BBS and press enter.
Rub the sleep out of your eyes, because you'll need to be on your
toes for the next couple of minutes (assuming you connect with the
board).  Once you've connected with the BBS, pay careful attention to
the status bar during script operation.  Are the "LOOK" statements
appropriate?  Watch the reaction of the BBS to what the script is
sending.  Everything OK?

        At this point, two things can happen -- the script could
execute perfectly from start to finish.  If so, congratulations!..you
are well on your way to having a rock-solid script.  Even if the
script does everything perfectly the first time, I would recommend
running it manually for at least three separate BBS sessions.  Be
sure to observe the process each time.

        The second possibility is that an alarm will sound somewhere
during the process..the macro screen will come up with one macro line
highlighted and an error message displayed on the bottom of the
screen.  Don't get discouraged if this happens, because it happens
even to the best script writers.  This possibility leads to the final
lesson in this first series -- Debugging -- coming up next lesson.

Jim