Partager via


Investigating a Skipped CETK Test Case (Windows CE 5.0)

Send Feedback

If a test case returns the TPR_SKIP code, the test case skipped. This might indicate an error. To investigate, verify that the OS design and hardware platform adequately support the CETK test case.

To investigate a skipped test case

  1. Verify that the OS design includes the Catalog items that correspond to the functionality exercised by the CETK test.

    If you chose not to add the corresponding Catalog items to the OS design, the TPR_SKIP result is expected and requires no further investigation.

    If you want the OS design to support the functionality exercised by the CETK test, add the corresponding Catalog items to the OS design, and then build a run-time image. For more information, see Adding an Item from the Catalog and Building a Run-Time Image.

  2. Verify that the OS design supports the functionality exercised by the test case.

    This requirement is more specific than the requirement that the OS design include the corresponding Catalog items. A test case might test a unit of functionality within a driver that is optional for drivers in its category. For example, the OS design might include a Catalog item of the correct driver category without supporting the functionality assessed by this specific test case.

    If you intentionally exclude the required support from the OS design, the TPR_SKIP result is expected and requires no further investigation.

    If you want the driver to support this functionality, modify the OS design, for example, by including a different driver that supports the required functionality. For more information about categories of driver, see Windows CE Drivers.

  3. Verify that the hardware platform satisfies the requirements of the OS design and the CETK test.

    If the hardware platform does not satisfy these requirements, a TPR_SKIP result typically indicates that that target device does not adequately support the functionality being tested. Reconsider the hardware for the target device or the OS design.

See Also

How to Analyze CETK Test Results to Debug a Driver | Investigating a Failed or Aborted CETK Test Case | Test Result Codes for a CETK Test Case

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.