Device interoperability starts with device operability. Device operability is defined as a device operating, without side effects, in typical end-user scenarios, without the presence of other USB devices. A USB device must be able to operate by itself in a system prior to pursuing device interoperability.
Device operability tests will ensure solid robust operation before moving on to interoperability testing.
There are two drive images that will be used when performing device operability and interoperability testing. These images are used to quickly refresh the system after lock-ups or system instability. These images would also be used after problem identification and resolution have been completed and retest is required.
By using these drive images, problems can be reproduced quickly and easily. Before each test in the checklists in Appendix B, there will be a statement as to which drive image to use prior to beginning testing.
This disk image is created from a fresh Linux distribution installed, possibly with a kernel upgrade performed. The USB drivers that are required to be installed are the UHCI host controller driver, the OHCI host controller driver and the usbdevfs driver. For non-hub devices, the appropriate kernel driver should also be installed.
The primary purpose of this drive image is to allow for initial device operability testing. This image will also be used when performing Device Under Test installation prior to the Gold Tree device installation. This image is taken immediately after operating system configuration and installation has completed.
This disk image is created from a fresh Linux distribution installation, with additional Gold Tree device drivers and associated applications installed if not already included.
The purpose of this drive image is for Gold Tree device interoperability testing. This image is taken after the operating system is installed and appropriate drivers are configured, and the entire Gold Tree of devices is attached and associated applications are installed.
It is assumed that the test machine has at least two partitions, one for the test configuration, and one as a test management environment. The space available for the test management environment needs to be contain sufficient free space to contain two additional files, each the size of the test configuration partition.
For example, given a 6G hard drive, create a 1G partition and a 5G partition. Install the development / test management environment on the 5G partition, ensuring that at least 2G remains free on this partition. Then install the test configuration on the 1G hard drive. Depending the Linux distribution installed, it may be neccessary to perform a kernel upgrade as described in the Linux Kernel HOWTO.
Make the first test image using dd. Typical usage, if the test configuration is installed on the first extended partition of the first ide drive would be dd if=/dev/hda5 of=CleanOSBuild bs=8192.
Install any additional drivers neccessary for the Gold Tree. With the standard Gold Tree, this should only require building and installing the drivers present in the kernel tree.
Make the second test image using dd. Typical usage, if the test configuration is installed on the first extended partition of the first ide drive would be dd if=/dev/hda5 of=GoldTreeBuild bs=8192.