CETK vs LTK – What’s the difference?

Understanding the nuances between test kits and what tests are appropriate for your device is very important. Since you are reading HoppeRx, I can assume Windows Mobile development, but the information given is valid for general WinCE development as well. The best way to explain is to give you a little history:

Back in the day (pre-Magneto) we had two separate test kits: the CETK and the LTK. The general embedded group (Windows CE) developed the CETK as a general testing framework that helped developers test upcoming platforms. CETK tests were comprehensive and intended for a broad range of device types – as such, not all tests were applicable for all types of devices. For example, if you device did not have a printer port – you simply did not run the printer port tests.

Contrary to this, the Windows Mobile team had the LTK. The LTK had a single purpose: to verify the existence of - and proper functionality of - each and every published platform requirement. Each test was designed to specifically check a requirement and as new requirements were written, new tests were designed to verify each Logo’d device complies with this requirement. The results from LTK tests are binary – they either PASS or FAIL, test result interpretation is not allowed. Interestingly, the LTK borrowed heavily on several appropriate CETK tests such as file system and GDI, but with modified command lines to make them appropriate for Windows Mobile devices. Fast forward to today…

Maintaining two separate kits is burdensome so we decided to merge the two kits with the biggest benefit being Windows Mobile customers can now enjoy the robust testing harness and log processing offered by the CETK. However, since the LTK must maintain its binary approach to testing (PASS or FAIL), separate testing nodes were created:

Windows CE Device Driver Test Kit This is the traditional CETK node and is intended for users with general embedded devices. This node contains many tests that are not appropriate for Windows Mobile devices.

Pocket PC Test Kit Pocket PC device developers should be using this node. It contains tests specifically tailored to your platform and you can find your LTK tests here.

Smartphone Test Kit Smartphone device developers should be using this node. It contains tests specifically tailored to your platform and you can find your LTK tests here. It does NOT contain inappropriate tests for this platform (such as the touch screen available in the above two nodes)

A confusing aspect of the above node system is that the CETK defaults to the Windows CE DDTK node – regardless of the type of device being used. Please keep a diligent eye out when running with the CETK and chose the correct node for your device.

I find users wanting to test their Windows Mobile devices with the tests offered in the Windows CE DDTK node – please resist the temptation. There is very little (if anything) offered in the general node appropriate for your device that is not already in the PPC or Smartphone node. You are free to run the parallel port test on your Smartphone but please don’t be surprised when the test fails (since there is no parallel port on your device).

 Lastly, many automated tests available in your device nodes’ require manual setup and/or manual verification steps that are available in the Windows Mobile test kit database, please use these as a guide to direct your automation test efforts.

Comments (0)

Skip to main content