Partager via


Camera Driver Name Tests (Compact 2013)

3/26/2014

The Camera Driver Name Tests ensure that the Camera Driver uses the right GUID and naming convention for DShow based drivers, pins and third party drivers.

Test Prerequisites

Your device must meet the following requirements before you run this test.

The following table shows the hardware requirements for this test.

Requirements

Description

Camera

The device must have camera functionality.

The following table shows the software requirements for this test.

Requirements

Description

Tux.exe

Required to execute the test.

Kato.dll

Required for logging test data.

CameraDriverNameTest.dll

Library that contains the test.

Camera driver

Driver developed for the camera hardware.

Subtests

The table below lists the subtests included in this test.

SubTest ID

Description

100

Enforce that all DShow based drivers are CAMX: devices.

101

Enforce that all PIN members of DShow based drivers are PIN.

102

Enforce that all third party based drivers are CAPX: devices.

Setting Up the Test

No setup required

Running the Test

Command Line Parameters:

This test executes the tux -o -d cameradrivernametest command line on default execution.

This test does not have any optional command-line parameters.

Verifying the Test

When the test completes a run, it will report a 'PASS' or 'FAIL' result for all subtests in the test log.

Troubleshooting the Test

If the test indicates the third party camera driver has an incorrect guid or device name, the OEM must adjust the guid to be the correct third party camera GUID, and all third party drivers must be named CAPX:.

See Also

Other Resources

Multimedia - Camera Tests