Running the Cellular Handset Tests

Logo Program: Windows Vista Client – Basic (x86, x64) and the Windows XP (x86) Logos

  1. Connect your Cellular Phone Device to the DTM Test Client Machine.

  2. Install your Cellular Phone Driver for the device under test on the Test Client Machine.

  3. From DTM studio, go to Explorers Device Console. Select your Machine Pool from the drop down list. Select View By Machine and then locate your device in Available Devices.

    • If DTM Studio is running on Windows Vista Ultimate, your device can found under Portable Devices.
    • If DTM Studio is running on Windows XP or other SKUs of Windows Vista, your device can be found under WPD. Because WPD is a relatively new device class, you may see a generic icon associated with the device node.
  4. Ensure that your device is powered on and registered in Device Console.

    • Right-click on the device and select View Device XML. Verify the entries such as DeviceID, DriverDate, DriverVersion, and ImagePath for your driver and device.
    • If your device does not appear or if you are seeing stale entries for previously connected devices, you may need to wait a few minutes and refresh the Device Console and/or reconnect the device.
  5. For Windows Vista Client (x86, x64), repeat steps 1 through 4 for one additional machine with an identical device. You need to setup two machines to complete the TS Plug and Play Redirection tests as part of your current submission.

  6. Create a new submission:

    a. From Device Console, select View By Submission.

    b. From the Submission drop down list, select <New Submission>.

    c. Select OS from the available options.

    d. Select Category: Device Submission.

    e. In the Create New Submission dialog box, select Portable Devices > Cellular Handsets.

    f. In the Create New Submission dialog box, select Basic under Qualification Level.

    g. Enter a name for your submission, and select your machine pool.

    h. Driver Install File (INF) [Required for submission]:

    • For Windows Vista Client Logo, browse and load both the driver and the TS-redirection driver INF files. The version numbers must match exactly with what you have installed on the DTM client test machines.
    • For Windows XP Logo, browse and load the driver INF file. The version number must match exactly with what you have installed on the DTM client test machine. The TS-redirection INF is not required.

    i. Click Finish to complete and load the new submission.

  7. Depending on how your INF file is authored, you may see multiple entries for your device. For the Windows Vista Client submission, select the device entry that corresponds to the driver INF, not the TS-redirection driver INF. For your convenience, one way to differentiate between the driver and the TS-redirection INF files is to author them with slightly different DriverVer or Manufacturer entries.

  8. With the correct device selected, from the Available Jobs, you can now add jobs from the first Cellular Handsets category. If your device connects via USB, you will see USB jobs in addition to the WPD Compliance Tests jobs. For requirements on running these jobs, please see Supplemental Tests or view the job details in Job Explorer.

    See the table below for a list of applicable jobs.

 

Logo Program: Windows Vista Client – Premium (x86, x64) and Windows 7 (x86, x64) Logos

  1. Connect a MTP Cellular Handset to the DTM Test Client Machine.

    Note  If the device supports mode switching, make sure that the device is in a mode that uses MTP.

  2. From DTM studio, go to Explorers Device Console. Select your Machine Pool from the drop down list. Select View By Machine and then locate your device in Available Devices. Your device can found under Portable Devices.

  3. Ensure that your device is powered on and registered in Device Console.

    • Right-click on the device and select View Device XML. Verify the entries such as ModelID, DeviceID, and ImagePath for your driver and device.
    • If your device does not appear or if you are seeing stale entries for previously connected devices, you may need to wait a few minutes and refresh the Device Console and/or reconnect the device.
  4. For Windows Vista Client (x86, x64), repeat steps 1 through 4 for one additional machine with an identical device. You need to setup two machines to complete the TS Plug and Play Redirection tests as part of your current submission.

  5. Create a new submission:

    a. From Device Console, select View By Submission.

    b. From the Submission drop down list, select <New Submission>.

    c. Select OS from the available options.

    d. Select Category: Device Submission.

    e. In the Create New Submission dialog box, select Portable Devices > Cellular Handsets.

    f. In the Create New Submission dialog box under Qualification Level, select Premium for Windows Vista or Logo for Windows 7**.**

    Note that if you are planning to submit for an Additional Qualification, that submission type may appear.

    g. Enter a name for your submission, and select your machine pool.

    h. Click Finish to complete and load the new submission.

  6. With the correct device selected, from the Available Jobs, you can now add jobs from the first Cellular Handsets category. If your device connects via USB, you will see USB jobs in addition to the WPD Compliance Tests jobs. For requirements on running these jobs, please see Portable Media Devices Tests or view the job details in Job Explorer.

The following table indicates which jobs are required based on connectivity type that must be run:

Test NameWindows XPWindows VistaWindows 7
USBBTIPOtherUSBBTIPOtherUSBBTIPOther
Connectivity Tests – PCI
PCI Hardware Compliance Test For a Single Device (PCIHCT)X
Connectivity Tests – USB
USB Address Description Test (Automated)XXX
USB Descriptor test (Automated)XXX
USB Device Control Requests (Automated)XXX
USB Enumeration Stress (Automated)XXX
USB Selective Suspend (Automated)XXX
USB Specification Compliance (Automated)XXX
USB Isochronous Alternate Interface Presence (Automated)XXX
USB HIDView (CV) (Manual)XXX
USB Device Framework (CV) (Manual)XXX
USB Serial Number (Automated)XXX
USB System Suspend Resume TestXXX
USB Disable Enable (Automated)XX
Connectivity Test – 1394
1394 Industry Certification Test ID Entry (MANUAL)XX
Device Fundamentals Tests
Web Services for DevicesXXXXXX
Run INFTest against a single INFXXXXXXXXX
Device Path ExerciserXXXXXXXXX
Plug and Play Driver TestXXXXX
Pnpdtest with concurrent IO in parallel with DevPathExerXX
Embedded Signature VerificationXX
WDF Logo TestsXX
Sleep Stress With IOXXX
Disable Enable With IOXXX
Common Scenario Stress With IOXXX
Reinstall With IOXX
Portable Devices Tests for Cellular Handset
WPD Compliance Tests - ALL SERVICESXXX
WPD Compliance Tests - CONTACT SERVICEXXX
WPD Compliance Tests - METADATA SERVICEXXX
WPD Compliance Tests - HINTS SERVICEXXX
WPD Compliance Tests - MODEL_IDXXX
WPD Compliance Tests - FUIDXXX
WPD Compliance Tests - NOTES SERVICEXXX
WPD Compliance Tests - RINGTONE SERVICEXXX
WPD Compliance Tests - STATUS SERVICEXXX
Verify Portable Media Device correctly supports Selective Suspend (MANUAL)X
WMDM Compliance TestsXXXXXXXX
WMDM Sync Test (MANUAL)XXXXXXXX
Digital Still Camera Windows HD Imaging Additional Qualification Test (MANUAL)XXXX
MTP Compliance Test – Cell PhonesX
Cell Phone [Windows Vista Premium Logo] MTP Compliance TestX
WPD Compliance Tests (WPDCopytest)XXXXXX
WPD Compliance Stress Tests (WPDCopytest)XXXXXX
WPD Compliance Tests (WPDCopytest – TS Redirection)X
WPD Compliance Stress Tests (WPDCopytest – TS Redirection)X
WPD Compliance Tests (MANUAL)XXX
WPD Compliance Stress Tests XXX

Many Cellular Handsets have the ability to connect to a PC using multiple modes. If the device is capable of connecting to the PC and appears as one of the following devices, additional testing is required:

  • If the device also functions as a Digital Media Renderer, Digital Media Server, or Digital Media Controller, you must submit results as a Network Media Device. For more information, please see Network Media Device Testing Overview.
  • A device that loads a driver for other modes must pass the Device Fundamental Tests in order to digitally sign the driver. For more information, please see Device Fundamental Tests.

Send feedback on this topic
Built on December 10, 2009