MDI test suite
auto_mdi [ <scenario_name> | all ]
Test suite name:
Provides formal verification
of MDI driver interface compliance
and tests MDI features and primitives.
Varies according to features tested.
master and slave
about 10 minutes for entire test suite
Number of test cases:
Number of invokable scenarios:
Set to master on the machine
where the driver being tested is installed
and to slave on the other machine.
Set to /dev/mdi/<driver>0
on both machines.
Specify any of the scenarios listed below.
Default is all, which runs all tests.
The following scenarios can be specified:
Test that bind state transitions are correct.
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.
Same as frametest except that broadcast addresses are used.
Same as frametest except that multicast broadcast addresses are used.
Send packets to self.
They should go out on the wire,
as well as be looped back.
A network monitor is needed to verify.
Test loopback to broadcast addresses.
All packet sizes are checked.
Test loopback when sent to
the token-ring multicast-broadcast address.
Test that multicasting works correctly.
Make sure all global symbols in driver's
start with the driver prefix.
© 2005 The SCO Group, Inc. All rights reserved.
OpenServer 6 and UnixWare (SVR5) HDK - June 2005