Return to README_TESTS CVS log

Up to [local] / trango / Net-Telnet-Trango / t

Annotation of trango/Net-Telnet-Trango/t/README_TESTS, Revision 1.3

1.2       andrew      1: For the network tests, there needs to be some hardware setup to make them pass.
                      2:
                      3: The hardware that these tests should be run against should not be in
                      4: production.  These tests may disrupt normal functioning of the hardware.
                      5:
                      6: There are three types of tests, each with different requirements.  AP Tests,
                      7: SU Tests and Association Tests.
                      8:
                      9: The configuration is read from a tests.cfg file in the t directory.  This
                     10: file is generated by Build.PL, but you can create or modify it yourself.
                     11: This file is a plain text file set up as key<tab>value.
                     12:
                     13: AP Tests:
                     14:
                     15: These tests run on an AP.  They require that you have an AP that is set up
                     16: and accessible through telnet.
                     17:
                     18: It uses two fields from the config file:
                     19:     AP:        the IP address of the AP
                     20:     AP_PASSWD: the password to login to the AP
                     21:
                     22: There are also a few subtests that can be run, these involve adding and
                     23: removing things from the SUDB.  Generally they are used with the Association
                     24: Tests, but they can be tested if you provide additional information.
                     25:
                     26: The fields used for these tests are as follow:
                     27:     SU_ID:  The SUID of the SU
                     28:     SU_MAC: The MAC address (all 12 digits, no spaces or punctuation)
                     29:
                     30:
                     31: SU Tests:
                     32:
                     33: These tests run on an SU.  They require that you have an SU that is set up
                     34: and accessible through telnet.
                     35:
                     36: It uses two fields from the config file:
                     37:     SU:        the IP address of the SU
                     38:     SU_PASSWD: the password to login to the SU
                     39:
                     40:
                     41: Association Tests:
                     42:
                     43: These tests require everything above is set up, and the SU should be set up
1.3     ! andrew     44: so that when you add an entry to the APs SUDB it will associate.  That means
        !            45: the SU should have that SUID set already, and the freq scantable should include
        !            46: the freq that is set on the AP.
1.2       andrew     47:
                     48: The tests will change the su password and su ipconfig, so the SU IP should
                     49: be in the same subnet as the AP IP.
                     50:
1.3     ! andrew     51: $RedRiver: README_TESTS,v 1.2 2007/02/06 21:15:28 andrew Exp $