WPD Compliance Stress Tests

This test exercises the driver by using the Windows Portable Device (WPD) API and validates that the device or driver complies with the Windows Hardware Certification requirements. This test is required to run for at least 24 hours as a prolonged stress test.

Note  

This test does not cover the following items:

• Legacy driver testing (only WPD class drivers are tested)

• Device-protocol-specific requirements (this testing is covered in separate certification tests)

• Digital Rights Management testing

Test details

Running the test

Before you run the test, complete the test setup as described in the test requirements: Device.Portable Testing Prerequisites.

Troubleshooting

For troubleshooting information, see Troubleshooting Device.Portable Testing.

When you are troubleshooting this test, note the following:

• This test supports verbose logging when in manual test case selection mode. When the application is running, in Options > Logging Options, select Destination: Window, and then select Level: 10.

• If no test cases are available from the test case selection tree, make sure that the device is plugged in.

For more information about requirements for portable device drivers, see Basic WPD Device Driver Requirements.

More Information

The WPD Compliance Stress Tests runs as a C++ application. When run outside HCK Studio, there is a test case selection user interface and test suites can be defined using test profiles. The test is fully automated and provides a Pass/Fail result for each requirement. The test validates the following for a WPD driver and the device connected to it.

Device/driver passes these common scenarios for content types and formats that it supports:

• Object hierarchy enumeration

• Object property retrieval

• Object resource reads from device

• Object resource writes to device

• Object deletion

• Power management

• Device-generated or driver-generated events

Device/driver supports the following known function categories:

• Required object properties and attributes

• Resources and attributes

Function category requirements

Recommended:

• WPD_FUNCTIONAL_CATEGORY_STORAGE

• WPD_FUNCTIONAL_CATEGORY_DEVICE

• WPD_FUNCTIONAL_CATEGORY_SMS

Optional:

• WPD_FUNCTIONAL_CATEGORY_STILL_IMAGE_CAPTURE

• WPD_FUNCTIONAL_CATEGORY_AUDIO_CAPTURE

Content type and format requirements

If a content type is not supported, the format support will not be verified. There are no strict requirements on the format or content type, because this is typically an implementation detail for device firmware. The driver can report support for any format or content type, as long as it passes the functional scenario tests that use objects of formats that it supports, like transfer, deletion, and enumeration. These formats and content types can serve as a guideline:

• Recommended content type: WPD_CONTENT_TYPE_AUDIO

• Recommended formats:

  • WPD_OBJECT_FORMAT_WMA

  • WPD_OBJECT_FORMAT_MP3

• Optional content type: WPD_CONTENT_TYPE_VIDEO

• Recommended format: WPD_OBJECT_FORMAT_WMV

• Optional content type: WPD_CONTENT_TYPE_IMAGE

• Recommended formats:

  • WPD_OBJECT_FORMAT_BMP

  • WPD_OBJECT_FORMAT_EXIF

  • WPD_OBJECT_FORMAT_GIF

  • WPD_OBJECT_FORMAT_ICON

  • WPD_OBJECT_FORMAT_JFIF

  • WPD_OBJECT_FORMAT_JP2

  • WPD_OBJECT_FORMAT_JPX

  • WPD_OBJECT_FORMAT_PNG

  • WPD_OBJECT_FORMAT_TIFF

• Optional content type: WPD_CONTENT_TYPE_DOCUMENT

• Optional formats:

  • WPD_OBJECT_FORMAT_HTML

  • WPD_OBJECT_FORMAT_TEXT

Command syntax

Note  

For command-line help for this test binary, type /h.

File list

Send comments about this topic to Microsoft