Camera Driver Preview and Capture Stream Functionality Verification (Compact 7)
3/12/2014
The Camera Driver Preview and Capture Stream Functionality Verification test verifies the functionality of the still, preview and capture streams on the camera driver.
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 the test data. |
CamIOTests.dll |
Library that contains the test cases. |
Camera driver |
Driver developed for the DirectShow capture model. |
Subtests
The table below lists the subtests included in this test.
SubTest ID | Description |
---|---|
1000 |
Still pin IO test. Triggers a capture event on the still stream. |
1001 |
Preview pin IO test. Creates a data stream of preview images from the camera driver and displays it on the screen. |
1002 |
Capture pin IO test. Creates a data stream of capture images from the camera driver and displays it on the screen. |
1003 |
Dropped frames test Frame dropping logic within the camera driver. |
Setting Up the Test
This test requires a DirectShow based camera driver.
Running the Test
This test executes the tux -o -d camiotests.dll command line on default execution.
This test does not have any optional command-line parameters.
Verifying the Test
When the test is complete running, it will report a 'PASS' or 'FAIL' result for all sub-tests in the test log.
Troubleshooting the Test
The following table shows troubleshooting hints for this test.
Failing test case | Solution |
---|---|
1001, 1002 |
Failure may be because of camera driver issues that prevent the driver from working under a DirectShow capture pipeline. |
1003 |
Failure may be because of the driver not setting or resetting the frame count and dropped frame count when putting the camera into stop/pause/run states. |
For additional platform specific issues, consult the CTK articles on the TechNet wiki.