Camera Driver Data Structure Verification (Compact 2013)
3/26/2014
The Camera Driver Data Structure Verification Test queries the camera driver for various properties and formats. The queries verify that the camera driver returns valid data structures.
You may want to run this test with a camera driver and verify the driver integration with DirectShow.
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. |
CamTestProperties.dll |
Library that contains the test. |
Camera driver |
Driver developed for the DirectShow capture model. |
Subtests
The table below lists the subtests included in this test.
SubTest ID |
Description |
|---|---|
1001-1013 |
CSProperty tests for confirming the driver's ability to read and write type, instance, datarange, name, and category properties. |
1101-1120 |
VideoProcAmp property tests VideoProcAmp properties in the driver, covering brightness, contrast, gamma, saturation, sharpness, white balance, color-enable, backlight compensation, gain, and hue. |
1201-1217 |
CameraControl property tests the CameraControl properties, covering exposure, focus, iris, zoom, pan, roll, and tilt, flash, focus. |
1301-1304 |
Verifies readability of the dropped frame count and invalid dropped frames buffers. |
1501-1505 |
Verifies readability and writability of the video control caps. |
1601-1605 |
Verifies readability and writability of the video compression caps. |
1701 |
Verifies readability of the driver metadata. |
Setting Up the Test
This test requires a DirectShow-based camera driver. No additional setup is needed.
Running the Test
The Camera Driver Data Structure Verification Test executes the tux -o -d camtestproperties.dll 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
The following table shows troubleshooting tips for this test.
Item |
Solution |
|---|---|
Test cases 1301-1304 are failing. |
This test does not verify dynamic frame dropping, only whether if you can query the property or not. Any test failures occur because driver bugs block the querying of the frame dropping data. |
Test cases 1501-1505 are failing. |
Failures occur because drivers incorrectly handle the getting and setting of video control caps. |
Test cases 1601-1605 are failing. |
This test is only valid if the camera driver supports video compression natively. (Video that outputted by the driver is pre-encoded as WMV.) Test failures occur if the driver does not retrieve or set these properties when the properties are reported as not being supported. |
General failures |
On a test failure, detailed failure information is given about which properties failed and why. Failures occur because of driver bugs when you access or modify the properties. Unsupported properties report as skipped. Therefore, when you develop a new driver, verify that no skipping of tests occurs for properties expected to have support. |