home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1994 #1
/
monster.zip
/
monster
/
RA
/
CONDR15B.ZIP
/
TESTING.DOC
< prev
Wrap
Text File
|
1994-02-13
|
2KB
|
54 lines
SYSTEM TESTING & DEBUGGING
Once you have CONNDOOR set up to where you think it is
ready to go, here are some hints and things to do before
you turn your users lose on it.
TEST.EXE -
The TEST.EXE program is nothing more than a dummy
program that exits with a "0" telling CONNDOOR that
the transfer was successful.
TEST.EXE can be entered as a protocol and the only
stipulation is that NONE be selected for Log Type since
TEST does not create a log.
When Download is selected with TEST in your BBSs local
mode, CONNDOOR will treat the download as successful
updating all logs and records as if the transfer was
successful.
When using TEST for upload testing, CONNDOOR will check
the upload directory for the file you listed for upload,
after the transfer is complete. If it finds a file of
the same name, it will treat it as a successful upload.
If the file is not found, CONNDOOR will treat it as a
failed upload.
EXAMPLE -
Rename or create any file "ABCD.ZIP" and place it in
the upload directory.
Enable CONNDOOR for upload from your BBS in the LOCAL
mode and select the TEST protocol.
Identify "ABCD.ZIP" for upload.
Start the transfer and "ABCD.ZIP" will be taken into
the system as a successful upload with all the
associated logs and records updated.
**** NOTE ****
Remember! Remove the TEST protocol entry from the
protocol list before you make CONNDOOR available to
your users.
This method of testing will also exercise the TAPE and
CDROM interface. I highly recommend doing the above
before certifying the system is ready for users.