Tux Architecture (Windows Embedded CE 6.0)
1/6/2010
The Tux client (Tux.exe) communicates with the Windows Embedded CE 6.0 Test Kit (CETK) server (CeTest.exe). The Tux client is the Tux engine, while the CETK server acts as a remote UI and administration tool. The Tux client is a console application that loads and executes Tux test modules. The CETK server remotely controls one or more Tux clients. With the CETK Server, you can load and unload Tux test modules, select test cases to run from each loaded test module, execute selected tests, and tally results.
The following list describes the advantages of this client/server architecture.
- The CETK server can control multiple Tux clients.
- Separate address spaces for the test engine and the UI minimize the possibility of conflicting code and errors.
- Separate address spaces allow the CETK server to keep running and provide results, even when the client causes a crash.
- The test engine has a small memory footprint and working set size.
- Tests do not compete with the test harness for the UI, because the entire UI for the harness is on the CETK server.
- You can remotely monitor the status of full-screen tests.
- You can port the Tux client to any platform that supports a minimal set of Microsoft® Win32® and Winsock APIs while taking advantage of the UI on the CETK server.
- You can run the Tux client without the CETK server in stand-alone mode, which is useful for batch testing.
In This Section
- Tux Command-Line Parameters
Describes the command line parameters available for Tux.
- Implementing a Tux Test Suite with TuxSkel
Tells how to use TuxSkel to implement a test suite
- Building a Tux DLL with Platform Builder
Tells how to build a Tux test library using Platform Builder
- Building a Tux DLL from the Command Line
Tells how to build a Tux test library from the command line