30, June, 1996
--------------

Test Plan for Telnet Dialout
----------------------------
Notes:
1. Procomm Plus for Windows 4.0 supports normal serial type file transfers 
   within a telnet session. Preferably testing can be performed using this
   telnet.
2. Sample telnet clients are
	- NCSA Telnet
	- Trumpet Telnet
	- Castle Rock Telnet
	- Procomm Plus for Windows 4.0
3. The Abort Output and Interrupt Process telnet commands are supported
   only by NCSA telnet.
4. Dialout can be performed on WAN ports that are marked as 'enabled' using
   ROUCON. Only those WAN ports that have not been taken up a remote access
   client or by routing will be used. Also dialout is only on ASYNC 
   non-direct-connect ports.

Testing
-------

General Working
---------------
1. Try to get to the dial-out screen.
1. Connect to some BBS (WildCat is a sample BBS that we have) using our
   dial-out and try out using all features of the BBS.
2. Connect to some IBM mainframe and tryout acting as a terminal.
3. Connect to some Unix host and try out acting as a terminal.
4. Check out all possible key actions in each screen and make sure that they
   take you somewhere logical.

Exhaustive Testing
------------------
(Use Procommm for Windows V4.0 for this)
1. Do dial-out on each of the WAN ports. On each WAN port, use atleast
   three different bauds, all parity, stop and data bit settings.
2. Do dial-out simultaneously on all WAN ports doing large file transfers.
3. TCP uses sequence numbers that are 32 bit's long. So keep doing repeated 
   file transfer's so that atleast one wrap around of the sequence numbers 
   takes place. For this atleast 2^32 bytes have to be transferred (is it
   possible is reasonable time?).

Simultaneous Access
-------------------
(Use NCSA telnet for this)
1. Simultaneous access can occur when a port that is chosen for dialout
   gets used for routing or by another telnet client who has init-ed faster.
   Between showing the 'available ports' menu and setting baud, parity, etc.
   the status of availablity of the port can change. Two scenarios must be
   reproduced and checked for
   - The chosen port subsequently gets used for routing -- In this case,
     routing should go on normally and the port should subsequently be
     denied for routing.
   - The chosen port is grabbed by another client who has init-ed faster --
     The current client should get a message saying the port has been
     taken away.

Connection Termination
----------------------
(Use NCSA telnet for this)
1. Once connection is setup, termination can occur in the following manner

	- Using the Abort Output telnet command -- desired action is that
  	  this should close the existing connection (show the string 
	  "hanging up...", etc) and reshow the WAN ports available menu.
	- Using the Interrupt Process telnet command -- this should terminate
	  the connection and exit the client
	- Terminating the client program
	- Rebooting the client -- The server has a 1/2 hour idle timeout on
	  each session. So after 1/2 an hour, the WAN port should again be
	  usable.

  The feature to test is that in all these cases, the WAN port that was in
  use should be made available for dialout or other purposes (after 1/2 in
  case of rebooting the client and almost immediately in case of other 
  termination methods).

   
File Transfers
--------------
(Use Procommm for Windows V4.0 for this)
1. Check that all possible file transfers protocols work in both the upload
   and download sequences. File transfers protocols include 
	ZMODEM, 
	KERMIT, 
	X-MODEM and variations, 
	Y-MODEM and variations, and 
	ASCII.
2. Check file transfer (upload and download) using 
	text   - small (<= 4K), medium (<= 128K), large (<= 2MB) files
	binary - small (<= 4K), medium (<= 128K), large (<= 2MB) files
   (NOTE that binary files cannot be transfered using some of the protocols)


Special Cases
-------------
(Use NCSA telnet for this)
1. When accepting passwords, echoing is turned off. So try each of the
   termination methods when requesting a password. Later try to run the
   client again and connect to the server. Make sure that echo-ing has been
   turned on properly again. This should specially be checked in the "ahort
   output" termination method.
2. Do WAN Chat when dial-out is going on. Dial-out should abort immediately.
3. Try out dial-out on a dial-on-demand WAN link. If the link is down by
   demand, then dial-out should NOT be able to access the port. If the link
   had never gone up, then dial-out should be able to access the port.
4. Check sequence when there is no dialout password provided to user.
5. What happens when the baud chosen is different from the one set on the
   BBS or Unix host?
6. Check that a port used for dialout is subsequently usable normally for
   routing.

Co-existence
------------
(Use Procomm Plus for Windows V4.0 or NCSA telnet for this)
1. Check that while one WAN is used for dial-out, other WAN's can route
   properly. Do this testing while the dial-out port is doing a file
   transfer of a large (2MB) file.



Other Apps
----------
1. Check that WAN Chat works as before. WAN chat can occur via serial
   command port or across the network. Try out both cases. Use MMV101 
   Command port 8 and ISDN router and make sure it works.
2. Check that our Windows based WANTalk can do WANCHAT via telnet properly.
3. Check out WAN Chat on each of the WAN ports.

Usability
---------
1. Check that all screens make sense and allow logical actions.
2. Check for spelling errors.
3. Have someone new use the system before and after explaining what is
   dialout and what is telnet client/server.
