Accelerometer MDD IOCTL (Compact 2013)
3/26/2014
The Accelerometer MDD IOCTL tests help to verify PDD integration and that APIs work as expected.
Power get/set IOCTLs, configuration IOCTLs and Get Caps APIs are called as part of this API testing.
Test Prerequisites
Your device must meet the following requirements before you run this test.
* Platform device containing an accelerometer.
* Associated accelerometer driver software.
Subtests
The table below lists the subtests included in this test.
SubTest ID |
Description |
|---|---|
2001 |
START IOCTL - Nominal |
2002 |
STOP IOCTL - Nominal |
2003 |
Sensor Get Caps - Nominal |
2004 |
Power Caps - Nominal |
2005 |
Power Set - Nominal |
2006 |
Power Get - Nominal |
2007 |
Set Config IOCTL - Nominal |
2102 |
START IOCTL - Input Validation |
2104 |
START IOCTL - Input Validation |
2106 |
START IOCTL - Input Validation |
2108 |
START IOCTL - Input Validation |
2109 |
START IOCTL - Input Validation |
2122 |
STOP IOCTL - Input Validation |
2123 |
STOP IOCTL - Input Validation |
2128 |
STOP IOCTL - Input Validation |
2142 |
Sensor Get Caps - Input Validation |
2143 |
Sensor Get Caps - Input Validation |
2144 |
Sensor Get Caps - Input Validation |
2145 |
Sensor Get Caps - Input Validation |
2162 |
Power Caps - Input Validation |
2182 |
Power Set - Input Validation |
2202 |
Power Get - Input Validation |
2222 |
Set Config IOCTL - Input Validation |
2223 |
Set Config IOCTL - Input Validation |
2224 |
Set Config IOCTL - Input Validation |
2225 |
Set Config IOCTL - Input Validation |
2226 |
Set Config IOCTL - Input Validation |
Setting Up the Test
This test has no additional requirements, beyond the standard test environment setup.
Running the Test
The test runs the following command line on default execution: tux -o -d acc_test.dll -x2001-2999
Verifying the Test
When the test completes running, verify that "PASS" appears in the test log for all sub-tests.
Troubleshooting the Test
* Ensure that the device image includes an accelerometer driver that employs the accelerometer API.
* Determine the point of failure and record the exact error message.
* If the source code is available, examine the point of failure in code to see if any additional information can be gathered about the failure domain.