Cellular Handset Testing Overview

  • Article

The procedures presented in this section outline the process for testing your Cellular Handset for proper functionality with the Microsoft Windows operating system. These procedures use the Microsoft Windows Logo Kit (WLK) and Driver Test Manager (DTM). To ensure full functionality, you must run all of the tests that the DTM identifies as required for the device. If your product provides bus-specific support, you must run the appropriate bus-specific tests in addition to the standard tests.

Using the Test Procedure Help Topics

Cellular Handset Testing Overview

 

Preparing for Cellular Handset Testing

 

Running the Cellular Handset Tests

 

Troubleshooting Cellular Handset Testing

Cellular Handset Tests

The list of tests needed to be run depends upon the capabilities of the device or system being tested. To see the complete list of tests that could be required for your device, see Running the Cellular Handset Tests.

Run time: Approximately 24-48 hours

Hardware requirements

The following hardware is required for Cellular Handset testing. Additional hardware may be required if the test device provides bus-specific support. See the test description for each bus-specific test to determine if there are additional hardware requirements.

  • System that supports USB 2.0
  • A USB cable for the device you are testing
  • For the Windows Vista Client Cellular Phone Logo, in order to also run the Terminal Server Plug and Play (PnP) tests, two computers running Microsoft Windows Vista are required. These two computers need to be of the same processor architecture (either x86 or amd64), and both need to have either an internal or external USB port connected. USB 2.0 is recommended.

Other Device Requirements

The following is required to run the Cellular Handset device testing component of the WLK:

Important There are specific tests that apply only to Cellular Handsets devices that install third-party (vendor-supplied) WPD drivers. If you are not providing a WPD driver for your Cellular Handset device, you are not required to run these tests for your device, even though the jobs might appear in the Device Console.

  • For Windows XP and Windows SP2, your device must appear under the Windows Portable Devices category in Device Manager.
  • For Windows Vista and later versions, your device must appear under the Portable Devices category in Device Manager.
  • Windows 7 devices must install with the Microsoft Media Transfer Protocol class driver. The device must connect to the PC in MTP Mode during testing.
  • The battery on the device should be fully charged before testing is started.
  • Some PTP or MTP devices are required to include sample content on the devices local storage before testing. If your devices meets any of the following criteria, include sample content on the device for each of the formats that the device supports to complete testing:
    • Device under test has a DCF compatible file system.
    • Device has read only stores.
    • Device does not support SendObject and SendObjectInfo.
    • Device does not support SendObject and SendObjectPropList
  • If the device supports removable media, the media must be added before testing.

Software requirements

The following software is required to run the Cellular Handset tests:

  • On Windows XP with Service Pack 2 (SP2), you must have the Windows Portable Devices and the User Mode Driver Framework binaries installed.

    Note If you are not sure whether or not you have these binaries installed on the client computer or you do not know how to install them, you can install Windows Media Player 11, which installs the binaries.

  • For Windows Vista Basic logo, the driver that came with your Windows Portable Devices cellular phone. The driver installation file (INF) must install the device as a WPD class with the following ClassGUID:

    • Class=WPD
    • ClassGUID={EEC5AD98-8080-425f-922A-DABF3DE3F69A}

Tester knowledge requirements

To run the Cellular Handset tests, testers must know how to accomplish the following tasks:

  • Switch a device to a computer connectivity mode before plugging it in.
  • Plug a device into a USB port of the computer and maintain the connectivity throughout the test run.
  • Provide continuous power to the device during throughout the test run.
  • Troubleshoot device installation by checking if the device is installed successfully in Device Manager or by looking at the SetupAPI device installation logs.

Send feedback on this topic
Built on December 10, 2009