Executing the test suites

After the systems are configured appropriately and the test suites are installed on both systems, you can run the appropriate tests for your device. To do this:

1. Put both the master and slave system into the correct init state for the test to be run. This guarantees a controlled networking environment and reliable test results. By default, the system boots to init state 3. To boot the system to init state 1:

   • Press the space bar at the SVR5 logo.

   • Enter initstate=1 at the boot: prompt.

   • Type go.

   To check the init state, type who -r.

   See ``Detailed description of the test suites'' for information about the init state required for each test suite and whether the suite is run on both the master and slave machines or only on the master machine.

   The tests that require run state 1 manually start and stop all networking daemons and stacks that are necessary to successfully run the test suite.

2. Log in as ndcert. The password for this user must be <Enter>.

3. For each test scenario your run, you must configure the parameters before running the test. The configuration files are in the ~/ndcert directory. Each test has its own file, with a name formed from the test name and the .cfg suffix, such as nd-mdi.cfg for the auto_mdi suite or nd-tcp.cfg for the auto_tcp suite. See ``Detailed description of the test suites'' for a list of the configuration parameters associated with each test suite.

4. Execute the script with <scenario_name> as an argument. Each test suite has a directory that contains a tet_scen scenario file that specifies what the test is.

The following error may occur while running these tests:

   ERROR: Lock file encountered on 'machine1'.  The tests may be running
   or may have terminated abnormally.  Please clean up the processes, remove
   the locks, and restart the tests.

   rm  -f  nd-*/bin/tet_lock