MDI test suite

Synopsis:

auto_mdi [ <scenario_name> | all ]

Configuration file:

nd-mdi.cfg

Test suite name:

nd-mdi

Summary:

Provides formal verification of MDI driver interface compliance and tests MDI features and primitives.

Media types:

Varies according to features tested.

Init state:

1

Executing machine(s)

master and slave

Execution time:

about 10 minutes for entire test suite

Number of test cases:

13

Number of invokable scenarios:

13

Configuration variables:

MASTERSLAVE

Set to master on the machine where the driver being tested is installed and to slave on the other machine.

DEVICE

Set to /dev/mdi/<driver>0 on both machines.

TEST_SCENARIO

Specify any of the scenarios listed below. Default is all, which runs all tests.

The following scenarios can be specified:

bind

Test that bind state transitions are correct.

frametest

Send and receive all packet sizes one at a time. Padding and every byte within each packet is verified to see that it did not change. Addressing is point-to-point.

framebcst

Same as frametest except that broadcast addresses are used.

framembcst

Same as frametest except that multicast broadcast addresses are used.

loopback

Send packets to self. They should go out on the wire, as well as be looped back. A network monitor is needed to verify.

loopbcst

Test loopback to broadcast addresses. All packet sizes are checked.

loopmbcst

Test loopback when sent to the token-ring multicast-broadcast address. Token-Ring only.

multicast

Test that multicasting works correctly.

macaddrtest

Test MACIOC_SETADDR, MACIOC_SETALLMCA, and MACIOC_DELALLMCA.

promisc

Test MACIOC_PROMISC.

symchk

Make sure all global symbols in driver's Space.c(DSP/4dsp) and Driver.o files start with the driver prefix.